Devices and Methods for Processing Touch Inputs with Instructions in a Web Page

ABSTRACT

An electronic device displays a content region including first content that contains an image; and, while displaying the first content, detects an input at a location that corresponds to the location of the image. In response, the electronic device, in accordance with a determination that the input includes an intensity above a respective threshold and that the image is associated with a link to second content that is different from the first content, displays a preview of the second content while maintaining display of at least a portion of the first content in the content region; and, in accordance with a determination that the input includes an intensity above the respective threshold and that the image is not associated with a link to additional content, displays an enlarged version of the image while maintaining display of at least a portion of the first content in the content region.

RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.14/866,489, filed Sep. 25, 2015, which claims priority to U.S.Provisional Application Ser. No. 62/184,816, filed Jun. 25, 2015,entitled “Devices and Methods for Processing Touch Inputs withInstructions in a Web Page,” and U.S. Provisional Application Ser. No.62/172,187, filed Jun. 7, 2015, entitled “Devices and Methods forProcessing Touch Inputs with Instructions in a Web Page,” all of whichare incorporated by reference herein in their entireties.

This application relates to U.S. Provisional Application Ser. No.62/129,954, filed Mar. 8, 2015, and U.S. Provisional Application Ser.No. 62/183,139, filed Jun. 22, 2015, both of which are incorporated byreference herein in their entireties.

TECHNICAL FIELD

This relates generally to electronic devices with touch-sensitivesurfaces, including but not limited to electronic devices withtouch-sensitive surfaces that display web pages.

BACKGROUND

The use of touch-sensitive surfaces as input devices for computers andother electronic computing devices has increased significantly in recentyears. Exemplary touch-sensitive surfaces include touchpads andtouch-screen displays. Such surfaces are widely used to manipulate userinterface objects on a display.

Exemplary manipulations include adjusting the position and/or size ofone or more user interface objects or activating buttons or openingfiles/applications represented by user interface objects, as well asassociating metadata with one or more user interface objects orotherwise manipulating user interfaces. Exemplary user interface objectsinclude digital images, video, text, icons, control elements such asbuttons and other graphics. A user will, in some circumstances, need toperform such manipulations on user interface objects in a filemanagement program (e.g., Finder from Apple Inc. of Cupertino, Calif.),an image management application (e.g., Aperture, iPhoto, Photos fromApple Inc. of Cupertino, Calif.), a digital content (e.g., videos andmusic) management application (e.g., iTunes from Apple Inc. ofCupertino, Calif.), a drawing application, a presentation application(e.g., Keynote from Apple Inc. of Cupertino, Calif.), a word processingapplication (e.g., Pages from Apple Inc. of Cupertino, Calif.), awebsite creation application (e.g., iWeb from Apple Inc. of Cupertino,Calif.), a disk authoring application (e.g., iDVD from Apple Inc. ofCupertino, Calif.), or a spreadsheet application (e.g., Numbers fromApple Inc. of Cupertino, Calif.).

But operations for performing these manipulations are predefined insoftware applications, and it is difficult to customize (e.g., change)performance of these manipulations, without revising the softwareapplications. For example, a revised software application (e.g., anupdated software application) needs to be downloaded and installed tocustomize (e.g., modify) performance of these manipulations. Thus,providing customized operations for modifying performance of suchmanipulations is time-consuming and inefficient, thereby wasting energy.This latter consideration is particularly important in battery-operateddevices.

SUMMARY

Accordingly, the present disclosure provides electronic devices withfaster, more efficient methods for providing customized processing oftouch inputs. Such methods and interfaces optionally complement orreplace conventional methods for providing customized processing oftouch inputs. Such methods and interfaces provide a more efficienthuman-machine interface by allowing customized processing of touchinputs. Further, such methods reduce the processing power consumed toprocess touch inputs, conserve power, reduceunnecessary/extraneous/repetitive inputs, and potentially reduce memoryusage. For battery-operated devices, such methods and interfacesconserve battery power and increase the time between battery charges.

The above deficiencies and other problems associated with userinterfaces for electronic devices with touch-sensitive surfaces arereduced or eliminated by the disclosed devices. In some embodiments, thedevice is a desktop computer. In some embodiments, the device isportable (e.g., a notebook computer, tablet computer, or handhelddevice). In some embodiments, the device is a personal electronic device(e.g., a wearable electronic device, such as a watch). In someembodiments, the device has a touchpad. In some embodiments, the devicehas a touch-sensitive display (also known as a “touch screen” or“touch-screen display”). In some embodiments, the device has a graphicaluser interface (GUI), one or more processors, memory and one or moremodules, programs or sets of instructions stored in the memory forperforming multiple functions. In some embodiments, the user interactswith the GUI primarily through stylus and/or finger contacts andgestures on the touch-sensitive surface. In some embodiments, thefunctions optionally include image editing, drawing, presenting, wordprocessing, spreadsheet making, game playing, telephoning, videoconferencing, e-mailing, instant messaging, workout support, digitalphotographing, digital videoing, web browsing, digital music playing,note taking, and/or digital video playing. Executable instructions forperforming these functions are, optionally, included in a non-transitorycomputer readable storage medium or other computer program productconfigured for execution by one or more processors. Alternatively, or inaddition, executable instructions for performing these functions are,optionally, included in a transitory computer-readable storage medium orother computer program product configured for execution by one or moreprocessors.

In accordance with some embodiments, a method is performed at anelectronic device with a display, a touch-sensitive surface, and one ormore sensors to detect intensity of contacts with the touch-sensitivesurface. The method includes: detecting a touch input on thetouch-sensitive surface at a first location that corresponds to thedisplayed portion of a web page on the display, while displaying a userinterface that corresponds to at least a portion of the web page on thedisplay, and while detecting the touch input on the touch-sensitivesurface, detecting an intensity of the touch input on thetouch-sensitive surface, determining whether the intensity of the touchinput on the touch-sensitive surface has changed from below a firstintensity threshold to above the first intensity threshold, and inresponse to determining that the intensity of the touch input on thetouch-sensitive surface has changed from below the first intensitythreshold to above the first intensity threshold, generating a forcedown event that is distinct from a mouse down event.

In accordance with some embodiments, a method is performed at anelectronic device with a display, a touch sensitive surface and one ormore sensors that are configured to detect the intensity of inputs onthe touch-sensitive surface. The method includes displaying, on thedisplay, a content region including first content that contains animage; and, while displaying the first content in the content region onthe display, detecting an input at a location that corresponds to thelocation of the image on the display. The method also includes, inresponse to detecting the input: in accordance with a determination thatthe input includes an intensity above a respective threshold and thatthe image is associated with a link to second content that is differentfrom the first content, displaying a preview of the second content whilemaintaining display of at least a portion of the first content in thecontent region; and, in accordance with a determination that the inputincludes an intensity above a respective threshold and that the image isnot associated with a link to additional content, displaying an enlargedversion of the image while maintaining display of at least a portion ofthe first content in the content region.

In accordance with some embodiments, an electronic device includes adisplay, a touch-sensitive surface, one or more sensors to detectintensity of contacts with the touch-sensitive surface, one or moreprocessors, memory, and one or more programs; the one or more programsare stored in the memory and configured to be executed by the one ormore processors and the one or more programs include instructions forperforming or causing performance of the operations of any of themethods described herein. In some embodiments, the electronic deviceincludes one or more sensors to detect signals from a stylus associatedwith the electronic device. In accordance with some embodiments, acomputer readable storage medium (e.g., a non-transitory computerreadable storage medium, or alternatively, a transitory computerreadable storage medium) has stored therein instructions which whenexecuted by an electronic device with a display, a touch-sensitivesurface, and one or more sensors to detect intensity of contacts withthe touch-sensitive surface, cause the device to perform or causeperformance of the operations of any of the methods described herein. Inaccordance with some embodiments, a graphical user interface on anelectronic device with a display, a touch-sensitive surface, one or moresensors to detect intensity of contacts with the touch-sensitivesurface, a memory, and one or more processors to execute one or moreprograms stored in the memory includes one or more of the elementsdisplayed in any of the methods described above, which are updated inresponse to inputs, as described in any of the methods described herein.In accordance with some embodiments, an electronic device includes: adisplay, a touch-sensitive surface, and one or more sensors to detectintensity of contacts with the touch-sensitive surface; and means forperforming or causing performance of the operations of any of themethods described herein. In accordance with some embodiments, aninformation processing apparatus, for use in an electronic device with adisplay and a touch-sensitive surface, and one or more sensors to detectintensity of contacts with the touch-sensitive surface, includes meansfor performing or causing performance of the operations of any of themethods described herein.

Thus, electronic devices with displays, touch-sensitive surfaces and oneor more sensors to detect intensity of contacts with the touch-sensitivesurface are provided with faster, more efficient methods and interfacesfor customized processing of touch inputs, thereby increasing theeffectiveness and efficiency of such devices, and user satisfaction withsuch devices. Furthermore, such methods and interfaces reduce processingpower, reduce memory usage, reduce battery usage, and/or reduceunnecessary or extraneous or repetitive inputs. Furthermore, suchmethods and interfaces may complement or replace conventional methodsfor customized processing of touch inputs.

BRIEF DESCRIPTION OF THE DRAWINGS

For a better understanding of the various described embodiments,reference should be made to the Description of Embodiments below, inconjunction with the following drawings in which like reference numeralsrefer to corresponding parts throughout the figures.

FIG. 1A is a block diagram illustrating a portable multifunction devicewith a touch-sensitive display in accordance with some embodiments.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments.

FIG. 1C is a block diagram illustrating transfer of an event object inaccordance with some embodiments.

FIG. 2 illustrates a portable multifunction device having a touch screenin accordance with some embodiments.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments.

FIG. 4 is a block diagram of an exemplary electronic stylus inaccordance with some embodiments.

FIGS. 5A-5B illustrate a positional state of a stylus relative to atouch-sensitive surface in accordance with some embodiments.

FIG. 6A illustrates an exemplary user interface for a menu ofapplications on a portable multifunction device in accordance with someembodiments.

FIG. 6B illustrates an exemplary user interface for a multifunctiondevice with a touch-sensitive surface that is separate from the displayin accordance with some embodiments.

FIGS. 6C-6E illustrate exemplary dynamic intensity thresholds inaccordance with some embodiments.

FIGS. 7A-7FF illustrate exemplary user interfaces for processing touchinputs with instructions in a web page in accordance with someembodiments.

FIGS. 8A-8C are flow diagrams illustrating a method of processing touchinputs with instructions in a web page in accordance with someembodiments.

FIG. 9 is a flow diagram illustrating a method of processing touchinputs based on displayed content in accordance with some embodiments.

DESCRIPTION OF EMBODIMENTS

Many electronic devices store applications to allow certainmanipulations of displayed user interface objects in response to touchinputs. Such applications are hardcoded for predefined operations thatdefine how touch inputs are to be processed. However, instructionsincluded in a document (e.g., JavaScript instructions in a web page) canbe used to provide customized operations. For example, instructions inthe document can be tailored based on the content of the document (e.g.,user interface objects defined in the document) to improve userexperience. Because such documents (e.g., web pages) can be readilymodified and used without installing them on the electronic devices,instructions included (e.g., embedded) in such documents offerflexibility as to how the content of the documents is delivered tousers. However, conventional methods and user interfaces (e.g., thoseoffered by conventional web pages with JavaScript instructions) areinefficient and/or incompatible in allowing operations based on anintensity of a touch input on a touch-sensitive surface. For example,generating a mouse moved event due to a change to the intensity of atouch input on the touch-sensitive surface without the touch inputmoving across the touch-sensitive surface can generate an error. Byproviding force events separate from mouse events, the describe methodsstreamline handling of changes to the intensity of a touch input on thetouch-sensitive surface. In addition, because the force events aregenerated using a separate software module (e.g., a Webkit),instructions included in web pages do not need to define operationsperformed by the separate software module, thereby simplifying theinstructions in the web pages. This also reduces the burden on webdevelopers and facilitates development of web pages that can moreefficiently handle changes to the intensity of a touch input on atouch-sensitive surface.

Below, FIGS. 1A-1B, 2, and 3 provide a description of exemplary devices.FIG. 4 provides a description of an exemplary electronic stylus. FIGS.5A-5B illustrate a positional state of a stylus relative to atouch-sensitive surface. FIGS. 6A-6B and 7A-7FF illustrate exemplaryuser interfaces for processing touch inputs with instructions in a webpage. FIGS. 8A-8C illustrate a flow diagram of a method of processingtouch inputs with instructions in a web page. FIG. 9 illustrates a flowdiagram of a method of processing touch inputs based on displayedcontent. The user interfaces in FIGS. 7A-7FF are used to illustrate theprocesses in FIGS. 8A-8C and FIG. 9.

Exemplary Devices

Reference will now be made in detail to embodiments, examples of whichare illustrated in the accompanying drawings. In the following detaileddescription, numerous specific details are set forth in order to providea thorough understanding of the various described embodiments. However,it will be apparent to one of ordinary skill in the art that the variousdescribed embodiments may be practiced without these specific details.In other instances, well-known methods, procedures, components,circuits, and networks have not been described in detail so as not tounnecessarily obscure aspects of the embodiments.

It will also be understood that, although the terms first, second, etc.are, in some instances, used herein to describe various elements, theseelements should not be limited by these terms. These terms are only usedto distinguish one element from another. For example, a first contactcould be termed a second contact, and, similarly, a second contact couldbe termed a first contact, without departing from the scope of thevarious described embodiments. The first contact and the second contactare both contacts, but they are not the same contact, unless the contextclearly indicates otherwise.

The terminology used in the description of the various describedembodiments herein is for the purpose of describing particularembodiments only and is not intended to be limiting. As used in thedescription of the various described embodiments and the appendedclaims, the singular forms “a,” “an,” and “the” are intended to includethe plural forms as well, unless the context clearly indicatesotherwise. It will also be understood that the term “and/or” as usedherein refers to and encompasses any and all possible combinations ofone or more of the associated listed items. It will be furtherunderstood that the terms “includes,” “including,” “comprises,” and/or“comprising,” when used in this specification, specify the presence ofstated features, integers, steps, operations, elements, and/orcomponents, but do not preclude the presence or addition of one or moreother features, integers, steps, operations, elements, components,and/or groups thereof.

As used herein, the term “if” is, optionally, construed to mean “when”or “upon” or “in response to determining” or “in response to detecting,”depending on the context. Similarly, the phrase “if it is determined” or“if [a stated condition or event] is detected” is, optionally, construedto mean “upon determining” or “in response to determining” or “upondetecting [the stated condition or event]” or “in response to detecting[the stated condition or event],” depending on the context.

Embodiments of electronic devices, user interfaces for such devices, andassociated processes for using such devices are described. In someembodiments, the device is a portable communications device, such as amobile telephone, that also contains other functions, such as PDA and/ormusic player functions. Exemplary embodiments of portable multifunctiondevices include, without limitation, the iPhone®, iPod Touch®, and iPad®devices from Apple Inc. of Cupertino, Calif. Other portable electronicdevices, such as laptops or tablet computers with touch-sensitivesurfaces (e.g., touch-screen displays and/or touchpads), are,optionally, used. It should also be understood that, in someembodiments, the device is not a portable communications device, but isa desktop computer with a touch-sensitive surface (e.g., a touch-screendisplay and/or a touchpad).

In the discussion that follows, an electronic device that includes adisplay and a touch-sensitive surface is described. It should beunderstood, however, that the electronic device optionally includes oneor more other physical user-interface devices, such as a physicalkeyboard, a mouse and/or a joystick.

The device typically supports a variety of applications, such as one ormore of the following: a note taking application, a drawing application,a presentation application, a word processing application, a websitecreation application, a disk authoring application, a spreadsheetapplication, a gaming application, a telephone application, a videoconferencing application, an e-mail application, an instant messagingapplication, a workout support application, a photo managementapplication, a digital camera application, a digital video cameraapplication, a web browsing application, a digital music playerapplication, and/or a digital video player application.

The various applications that are executed on the device optionally useat least one common physical user-interface device, such as thetouch-sensitive surface. One or more functions of the touch-sensitivesurface as well as corresponding information displayed on the deviceare, optionally, adjusted and/or varied from one application to the nextand/or within a respective application. In this way, a common physicalarchitecture (such as the touch-sensitive surface) of the deviceoptionally supports the variety of applications with user interfacesthat are intuitive and transparent to the user.

Attention is now directed toward embodiments of portable devices withtouch-sensitive displays. FIG. 1A is a block diagram illustratingportable multifunction device 100 with touch-sensitive display system112 in accordance with some embodiments. Touch-sensitive display system112 is sometimes called a “touch screen” for convenience, and issometimes simply called a touch-sensitive display. Device 100 includesmemory 102 (which optionally includes one or more non-transitorycomputer readable storage mediums), memory controller 122, one or moreprocessing units (CPUs) 120, peripherals interface 118, RF circuitry108, audio circuitry 110, speaker 111, microphone 113, input/output(I/O) subsystem 106, other input or control devices 116, and externalport 124. Device 100 optionally includes one or more optical sensors164. Device 100 optionally includes one or more intensity sensors 165for detecting intensity of contacts on device 100 (e.g., atouch-sensitive surface such as touch-sensitive display system 112 ofdevice 100). Device 100 optionally includes one or more tactile outputgenerators 163 for generating tactile outputs on device 100 (e.g.,generating tactile outputs on a touch-sensitive surface such astouch-sensitive display system 112 of device 100 or touchpad 355 ofdevice 300). These components optionally communicate over one or morecommunication buses or signal lines 103.

As used in the specification and claims, the term “tactile output”refers to physical displacement of a device relative to a previousposition of the device, physical displacement of a component (e.g., atouch-sensitive surface) of a device relative to another component(e.g., housing) of the device, or displacement of the component relativeto a center of mass of the device that will be detected by a user withthe user's sense of touch. For example, in situations where the deviceor the component of the device is in contact with a surface of a userthat is sensitive to touch (e.g., a finger, palm, or other part of auser's hand), the tactile output generated by the physical displacementwill be interpreted by the user as a tactile sensation corresponding toa perceived change in physical characteristics of the device or thecomponent of the device. For example, movement of a touch-sensitivesurface (e.g., a touch-sensitive display or trackpad) is, optionally,interpreted by the user as a “down click” or “up click” of a physicalactuator button. In some cases, a user will feel a tactile sensationsuch as an “down click” or “up click” even when there is no movement ofa physical actuator button associated with the touch-sensitive surfacethat is physically pressed (e.g., displaced) by the user's movements. Asanother example, movement of the touch-sensitive surface is, optionally,interpreted or sensed by the user as “roughness” of the touch-sensitivesurface, even when there is no change in smoothness of thetouch-sensitive surface. While such interpretations of touch by a userwill be subject to the individualized sensory perceptions of the user,there are many sensory perceptions of touch that are common to a largemajority of users. Thus, when a tactile output is described ascorresponding to a particular sensory perception of a user (e.g., an “upclick,” a “down click,” “roughness”), unless otherwise stated, thegenerated tactile output corresponds to physical displacement of thedevice or a component thereof that will generate the described sensoryperception for a typical (or average) user.

It should be appreciated that device 100 is only one example of aportable multifunction device, and that device 100 optionally has moreor fewer components than shown, optionally combines two or morecomponents, or optionally has a different configuration or arrangementof the components. The various components shown in FIG. 1A areimplemented in hardware, software, firmware, or a combination thereof,including one or more signal processing and/or application specificintegrated circuits.

Memory 102 optionally includes high-speed random access memory andoptionally also includes non-volatile memory, such as one or moremagnetic disk storage devices, flash memory devices, or othernon-volatile solid-state memory devices. Access to memory 102 by othercomponents of device 100, such as CPU(s) 120 and the peripheralsinterface 118, is, optionally, controlled by memory controller 122.

Peripherals interface 118 can be used to couple input and outputperipherals of the device to CPU(s) 120 and memory 102. The one or moreprocessors 120 run or execute various software programs and/or sets ofinstructions stored in memory 102 to perform various functions fordevice 100 and to process data.

In some embodiments, peripherals interface 118, CPU(s) 120, and memorycontroller 122 are, optionally, implemented on a single chip, such aschip 104. In some other embodiments, they are, optionally, implementedon separate chips.

RF (radio frequency) circuitry 108 receives and sends RF signals, alsocalled electromagnetic signals. RF circuitry 108 converts electricalsignals to/from electromagnetic signals and communicates withcommunications networks and other communications devices via theelectromagnetic signals. RF circuitry 108 optionally includes well-knowncircuitry for performing these functions, including but not limited toan antenna system, an RF transceiver, one or more amplifiers, a tuner,one or more oscillators, a digital signal processor, a CODEC chipset, asubscriber identity module (SIM) card, memory, and so forth. RFcircuitry 108 optionally communicates with networks, such as theInternet, also referred to as the World Wide Web (WWW), an intranetand/or a wireless network, such as a cellular telephone network, awireless local area network (LAN) and/or a metropolitan area network(MAN), and other devices by wireless communication. The wirelesscommunication optionally uses any of a plurality of communicationsstandards, protocols and technologies, including but not limited toGlobal System for Mobile Communications (GSM), Enhanced Data GSMEnvironment (EDGE), high-speed downlink packet access (HSDPA),high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO),HSPA, HSPA+, Dual-Cell HSPA (DC-HSPDA), long term evolution (LTE), nearfield communication (NFC), wideband code division multiple access(W-CDMA), code division multiple access (CDMA), time division multipleaccess (TDMA), Bluetooth, Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.11a,IEEE 802.11ac, IEEE 802.11ax, IEEE 802.11b, IEEE 802.11g and/or IEEE802.11n), voice over Internet Protocol (VoIP), Wi-MAX, a protocol fore-mail (e.g., Internet message access protocol (IMAP) and/or post officeprotocol (POP)), instant messaging (e.g., extensible messaging andpresence protocol (XMPP), Session Initiation Protocol for InstantMessaging and Presence Leveraging Extensions (SIMPLE), Instant Messagingand Presence Service (IMPS)), and/or Short Message Service (SMS), or anyother suitable communication protocol, including communication protocolsnot yet developed as of the filing date of this document.

Audio circuitry 110, speaker 111, and microphone 113 provide an audiointerface between a user and device 100. Audio circuitry 110 receivesaudio data from peripherals interface 118, converts the audio data to anelectrical signal, and transmits the electrical signal to speaker 111.Speaker 111 converts the electrical signal to human-audible sound waves.Audio circuitry 110 also receives electrical signals converted bymicrophone 113 from sound waves. Audio circuitry 110 converts theelectrical signal to audio data and transmits the audio data toperipherals interface 118 for processing. Audio data is, optionally,retrieved from and/or transmitted to memory 102 and/or RF circuitry 108by peripherals interface 118. In some embodiments, audio circuitry 110also includes a headset jack (e.g., 212, FIG. 2). The headset jackprovides an interface between audio circuitry 110 and removable audioinput/output peripherals, such as output-only headphones or a headsetwith both output (e.g., a headphone for one or both ears) and input(e.g., a microphone).

I/O subsystem 106 couples input/output peripherals on device 100, suchas touch-sensitive display system 112 and other input or control devices116, with peripherals interface 118. I/O subsystem 106 optionallyincludes display controller 156, optical sensor controller 158,intensity sensor controller 159, haptic feedback controller 161, and oneor more input controllers 160 for other input or control devices. Theone or more input controllers 160 receive/send electrical signalsfrom/to other input or control devices 116. The other input or controldevices 116 optionally include physical buttons (e.g., push buttons,rocker buttons, etc.), dials, slider switches, joysticks, click wheels,and so forth. In some alternate embodiments, input controller(s) 160are, optionally, coupled with any (or none) of the following: akeyboard, infrared port, USB port, stylus, and/or a pointer device suchas a mouse. The one or more buttons (e.g., 208, FIG. 2) optionallyinclude an up/down button for volume control of speaker 111 and/ormicrophone 113. The one or more buttons optionally include a push button(e.g., 206, FIG. 2).

Touch-sensitive display system 112 provides an input interface and anoutput interface between the device and a user. Display controller 156receives and/or sends electrical signals from/to touch-sensitive displaysystem 112. Touch-sensitive display system 112 displays visual output tothe user. The visual output optionally includes graphics, text, icons,video, and any combination thereof (collectively termed “graphics”). Insome embodiments, some or all of the visual output corresponds touser-interface objects.

Touch-sensitive display system 112 has a touch-sensitive surface, sensoror set of sensors that accepts input from the user based onhaptic/tactile contact. Touch-sensitive display system 112 and displaycontroller 156 (along with any associated modules and/or sets ofinstructions in memory 102) detect contact (and any movement or breakingof the contact) on touch-sensitive display system 112 and converts thedetected contact into interaction with user-interface objects (e.g., oneor more soft keys, icons, web pages or images) that are displayed ontouch-sensitive display system 112. In some embodiments, a point ofcontact between touch-sensitive display system 112 and the usercorresponds to a finger of the user or a stylus.

Touch-sensitive display system 112 optionally uses LCD (liquid crystaldisplay) technology, LPD (light emitting polymer display) technology, orLED (light emitting diode) technology, although other displaytechnologies are used in other embodiments. Touch-sensitive displaysystem 112 and display controller 156 optionally detect contact and anymovement or breaking thereof using any of a plurality of touch sensingtechnologies now known or later developed, including but not limited tocapacitive, resistive, infrared, and surface acoustic wave technologies,as well as other proximity sensor arrays or other elements fordetermining one or more points of contact with touch-sensitive displaysystem 112. In some embodiments, projected mutual capacitance sensingtechnology is used, such as that found in the iPhone®, iPod Touch®, andiPad® from Apple Inc. of Cupertino, Calif.

Touch-sensitive display system 112 optionally has a video resolution inexcess of 100 dpi. In some embodiments, the touch screen videoresolution is in excess of 400 dpi (e.g., 500 dpi, 800 dpi, or greater).The user optionally makes contact with touch-sensitive display system112 using any suitable object or appendage, such as a stylus, a finger,and so forth. In some embodiments, the user interface is designed towork with finger-based contacts and gestures, which can be less precisethan stylus-based input due to the larger area of contact of a finger onthe touch screen. In some embodiments, the device translates the roughfinger-based input into a precise pointer/cursor position or command forperforming the actions desired by the user.

In some embodiments, in addition to the touch screen, device 100optionally includes a touchpad (not shown) for activating ordeactivating particular functions. In some embodiments, the touchpad isa touch-sensitive area of the device that, unlike the touch screen, doesnot display visual output. The touchpad is, optionally, atouch-sensitive surface that is separate from touch-sensitive displaysystem 112 or an extension of the touch-sensitive surface formed by thetouch screen.

Device 100 also includes power system 162 for powering the variouscomponents. Power system 162 optionally includes a power managementsystem, one or more power sources (e.g., battery, alternating current(AC)), a recharging system, a power failure detection circuit, a powerconverter or inverter, a power status indicator (e.g., a light-emittingdiode (LED)) and any other components associated with the generation,management and distribution of power in portable devices.

Device 100 optionally also includes one or more optical sensors 164.FIG. 1A shows an optical sensor coupled with optical sensor controller158 in I/O subsystem 106. Optical sensor(s) 164 optionally includecharge-coupled device (CCD) or complementary metal-oxide semiconductor(CMOS) phototransistors. Optical sensor(s) 164 receive light from theenvironment, projected through one or more lens, and converts the lightto data representing an image. In conjunction with imaging module 143(also called a camera module), optical sensor(s) 164 optionally capturestill images and/or video. In some embodiments, an optical sensor islocated on the back of device 100, opposite touch-sensitive displaysystem 112 on the front of the device, so that the touch screen isenabled for use as a viewfinder for still and/or video imageacquisition. In some embodiments, another optical sensor is located onthe front of the device so that the user's image is obtained (e.g., forselfies, for videoconferencing while the user views the other videoconference participants on the touch screen, etc.).

Device 100 optionally also includes one or more contact intensitysensors 165. FIG. 1A shows a contact intensity sensor coupled withintensity sensor controller 159 in I/O subsystem 106. Contact intensitysensor(s) 165 optionally include one or more piezoresistive straingauges, capacitive force sensors, electric force sensors, piezoelectricforce sensors, optical force sensors, capacitive touch-sensitivesurfaces, or other intensity sensors (e.g., sensors used to measure theforce (or pressure) of a contact on a touch-sensitive surface). Contactintensity sensor(s) 165 receive contact intensity information (e.g.,pressure information or a proxy for pressure information) from theenvironment. In some embodiments, at least one contact intensity sensoris collocated with, or proximate to, a touch-sensitive surface (e.g.,touch-sensitive display system 112). In some embodiments, at least onecontact intensity sensor is located on the back of device 100, oppositetouch-screen display system 112 which is located on the front of device100.

Device 100 optionally also includes one or more proximity sensors 166.FIG. 1A shows proximity sensor 166 coupled with peripherals interface118. Alternately, proximity sensor 166 is coupled with input controller160 in I/O subsystem 106. In some embodiments, the proximity sensorturns off and disables touch-sensitive display system 112 when themultifunction device is placed near the user's ear (e.g., when the useris making a phone call).

Device 100 optionally also includes one or more tactile outputgenerators 163. FIG. 1A shows a tactile output generator coupled withhaptic feedback controller 161 in I/O subsystem 106. Tactile outputgenerator(s) 163 optionally include one or more electroacoustic devicessuch as speakers or other audio components and/or electromechanicaldevices that convert energy into linear motion such as a motor,solenoid, electroactive polymer, piezoelectric actuator, electrostaticactuator, or other tactile output generating component (e.g., acomponent that converts electrical signals into tactile outputs on thedevice). In some embodiments, tactile output generator(s) 163 receivetactile feedback generation instructions from haptic feedback module 133and generates tactile outputs on device 100 that are capable of beingsensed by a user of device 100. In some embodiments, at least onetactile output generator is collocated with, or proximate to, atouch-sensitive surface (e.g., touch-sensitive display system 112) and,optionally, generates a tactile output by moving the touch-sensitivesurface vertically (e.g., in/out of a surface of device 100) orlaterally (e.g., back and forth in the same plane as a surface of device100). In some embodiments, at least one tactile output generator sensoris located on the back of device 100, opposite touch-sensitive displaysystem 112, which is located on the front of device 100.

Device 100 optionally also includes one or more accelerometers 167,gyroscopes 168, and/or magnetometers 169 (e.g., as part of an inertialmeasurement unit (IMU)) for obtaining information concerning theposition (e.g., attitude) of the device. FIG. 1A shows sensors 167, 168,and 169 coupled with peripherals interface 118. Alternately, sensors167, 168, and 169 are, optionally, coupled with an input controller 160in I/O subsystem 106. In some embodiments, information is displayed onthe touch-screen display in a portrait view or a landscape view based onan analysis of data received from the one or more accelerometers. Device100 optionally includes a GPS (or GLONASS or other global navigationsystem) receiver (not shown) for obtaining information concerning thelocation of device 100.

In some embodiments, the software components stored in memory 102include operating system 126, communication module (or set ofinstructions) 128, contact/motion module (or set of instructions) 130,position module (or set of instructions) 131, graphics module (or set ofinstructions) 132, haptic feedback module (or set of instructions) 133,text input module (or set of instructions) 134, Global PositioningSystem (GPS) module (or set of instructions) 135, applications (or setsof instructions) 136, web engine module 175, and one or more web pages185. Furthermore, in some embodiments, memory 102 stores device/globalinternal state 157, as shown in FIGS. 1A and 3. Device/global internalstate 157 includes one or more of: active application state, indicatingwhich applications, if any, are currently active; display state,indicating what applications, views or other information occupy variousregions of touch-sensitive display system 112; sensor state, includinginformation obtained from the device's various sensors and other inputor control devices 116; and location and/or positional informationconcerning the device's location and/or attitude.

Operating system 126 (e.g., iOS, Darwin, RTXC, LINUX, UNIX, OS X,WINDOWS, or an embedded operating system such as VxWorks) includesvarious software components and/or drivers for controlling and managinggeneral system tasks (e.g., memory management, storage device control,power management, etc.) and facilitates communication between varioushardware and software components.

Communication module 128 facilitates communication with other devicesover one or more external ports 124 and also includes various softwarecomponents for handling data received by RF circuitry 108 and/orexternal port 124. External port 124 (e.g., Universal Serial Bus (USB),FIREWIRE, etc.) is adapted for coupling directly to other devices orindirectly over a network (e.g., the Internet, wireless LAN, etc.). Insome embodiments, the external port is a multi-pin (e.g., 30-pin)connector that is the same as, or similar to and/or compatible with the30-pin connector used in some iPhone®, iPod Touch®, and iPad® devicesfrom Apple Inc. of Cupertino, Calif. In some embodiments, the externalport is a Lightning connector that is the same as, or similar to and/orcompatible with the Lightning connector used in some iPhone®, iPodTouch®, and iPad® devices from Apple Inc. of Cupertino, Calif.

Contact/motion module 130 optionally detects contact withtouch-sensitive display system 112 (in conjunction with displaycontroller 156) and other touch-sensitive devices (e.g., a touchpad orphysical click wheel). Contact/motion module 130 includes softwarecomponents for performing various operations related to detection ofcontact (e.g., by a finger or by a stylus), such as determining ifcontact has occurred (e.g., detecting a finger-down event), determiningan intensity of the contact (e.g., the force or pressure of the contactor a substitute for the force or pressure of the contact), determiningif there is movement of the contact and tracking the movement across thetouch-sensitive surface (e.g., detecting one or more finger-draggingevents), and determining if the contact has ceased (e.g., detecting afinger-up event or a break in contact). Contact/motion module 130receives contact data from the touch-sensitive surface. Determiningmovement of the point of contact, which is represented by a series ofcontact data, optionally includes determining speed (magnitude),velocity (magnitude and direction), and/or an acceleration (a change inmagnitude and/or direction) of the point of contact. These operationsare, optionally, applied to single contacts (e.g., one finger contactsor stylus contacts) or to multiple simultaneous contacts (e.g.,“multitouch”/multiple finger contacts and/or stylus contacts). In someembodiments, contact/motion module 130 and display controller 156 detectcontact on a touchpad.

Contact/motion module 130 optionally detects a gesture input by a user.Different gestures on the touch-sensitive surface have different contactpatterns (e.g., different motions, timings, and/or intensities ofdetected contacts). Thus, a gesture is, optionally, detected bydetecting a particular contact pattern. For example, detecting a fingertap gesture includes detecting a finger-down event followed by detectinga finger-up (lift off) event at the same position (or substantially thesame position) as the finger-down event (e.g., at the position of anicon). As another example, detecting a finger swipe gesture on thetouch-sensitive surface includes detecting a finger-down event followedby detecting one or more finger-dragging events, and subsequentlyfollowed by detecting a finger-up (lift off) event. Similarly, tap,swipe, drag, and other gestures are optionally detected for a stylus bydetecting a particular contact pattern for the stylus.

Position module 131, in conjunction with accelerometers 167, gyroscopes168, and/or magnetometers 169, optionally detects positional informationconcerning the device, such as the device's attitude (roll, pitch,and/or yaw) in a particular frame of reference. Position module 130includes software components for performing various operations relatedto detecting the position of the device and detecting changes to theposition of the device. In some embodiments, position module 131 usesinformation received from a stylus being used with the device to detectpositional information concerning the stylus, such as detecting thepositional state of the stylus relative to the device and detectingchanges to the positional state of the stylus.

Graphics module 132 includes various known software components forrendering and displaying graphics on touch-sensitive display system 112or other display, including components for changing the visual impact(e.g., brightness, transparency, saturation, contrast or other visualproperty) of graphics that are displayed. As used herein, the term“graphics” includes any object that can be displayed to a user,including without limitation text, web pages, icons (such asuser-interface objects including soft keys), digital images, videos,animations and the like.

In some embodiments, graphics module 132 stores data representinggraphics to be used. Each graphic is, optionally, assigned acorresponding code. Graphics module 132 receives, from applicationsetc., one or more codes specifying graphics to be displayed along with,if necessary, coordinate data and other graphic property data, and thengenerates screen image data to output to display controller 156.

Haptic feedback module 133 includes various software components forgenerating instructions (e.g., instructions used by haptic feedbackcontroller 161) to produce tactile outputs using tactile outputgenerator(s) 163 at one or more locations on device 100 in response touser interactions with device 100.

Text input module 134, which is, optionally, a component of graphicsmodule 132, provides soft keyboards for entering text in variousapplications (e.g., contacts 137, e-mail 140, IM 141, browser 147, andany other application that needs text input).

GPS module 135 determines the location of the device and provides thisinformation for use in various applications (e.g., to telephone 138 foruse in location-based dialing, to camera 143 as picture/video metadata,and to applications that provide location-based services such as weatherwidgets, local yellow page widgets, and map/navigation widgets).

Applications 136 optionally include the following modules (or sets ofinstructions), or a subset or superset thereof:

-   contacts module 137 (sometimes called an address book or contact    list);-   telephone module 138;-   video conferencing module 139;-   e-mail client module 140;-   instant messaging (IM) module 141;-   workout support module 142;-   camera module 143 for still and/or video images;-   image management module 144;-   browser module 147;-   calendar module 148;-   widget modules 149, which optionally include one or more of: weather    widget 149-1, stocks widget 149-2, calculator widget 149-3, alarm    clock widget 149-4, dictionary widget 149-5, and other widgets    obtained by the user, as well as user-created widgets 149-6;-   widget creator module 150 for making user-created widgets 149-6;-   search module 151;-   video and music player module 152, which is, optionally, made up of    a video player module and a music player module;-   notes module 153;-   map module 154; and/or-   online video module 155.

Examples of other applications 136 that are, optionally, stored inmemory 102 include other word processing applications, other imageediting applications, drawing applications, presentation applications,JAVA-enabled applications, encryption, digital rights management, voicerecognition, and voice replication.

Web Engine Module 175 (also called a web browser engine, layout engine,rendering engine, or Webkit) processes marked up content (e.g.,HyperText Markup Language (HTML) documents, Extensible Markup Language(XML) documents, etc.). For example, web engine module 175 prepares alayout of the marked up content for display. In some embodiments, webengine module 175 processes instructions included in the marked upcontent (e.g., JavaScript instructions in web pages 185, etc.). In someembodiments, web engine module 175 is included in operating system 126.In some embodiments, web engine module 175 is integrated with browsermodule 147.

In conjunction with touch-sensitive display system 112, displaycontroller 156, contact module 130, graphics module 132, and text inputmodule 134, contacts module 137 includes executable instructions tomanage an address book or contact list (e.g., stored in applicationinternal state 192 of contacts module 137 in memory 102 or memory 370),including: adding name(s) to the address book; deleting name(s) from theaddress book; associating telephone number(s), e-mail address(es),physical address(es) or other information with a name; associating animage with a name; categorizing and sorting names; providing telephonenumbers and/or e-mail addresses to initiate and/or facilitatecommunications by telephone 138, video conference 139, e-mail 140, or IM141; and so forth.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch-sensitive display system 112, display controller156, contact module 130, graphics module 132, and text input module 134,telephone module 138 includes executable instructions to enter asequence of characters corresponding to a telephone number, access oneor more telephone numbers in address book 137, modify a telephone numberthat has been entered, dial a respective telephone number, conduct aconversation and disconnect or hang up when the conversation iscompleted. As noted above, the wireless communication optionally usesany of a plurality of communications standards, protocols andtechnologies.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch-sensitive display system 112, display controller156, optical sensor(s) 164, optical sensor controller 158, contactmodule 130, graphics module 132, text input module 134, contact list137, and telephone module 138, videoconferencing module 139 includesexecutable instructions to initiate, conduct, and terminate a videoconference between a user and one or more other participants inaccordance with user instructions.

In conjunction with RF circuitry 108, touch-sensitive display system112, display controller 156, contact module 130, graphics module 132,and text input module 134, e-mail client module 140 includes executableinstructions to create, send, receive, and manage e-mail in response touser instructions. In conjunction with image management module 144,e-mail client module 140 makes it very easy to create and send e-mailswith still or video images taken with camera module 143.

In conjunction with RF circuitry 108, touch-sensitive display system112, display controller 156, contact module 130, graphics module 132,and text input module 134, the instant messaging module 141 includesexecutable instructions to enter a sequence of characters correspondingto an instant message, to modify previously entered characters, totransmit a respective instant message (for example, using a ShortMessage Service (SMS) or Multimedia Message Service (MMS) protocol fortelephony-based instant messages or using XMPP, SIMPLE, Apple PushNotification Service (APNs) or IMPS for Internet-based instantmessages), to receive instant messages and to view received instantmessages. In some embodiments, transmitted and/or received instantmessages optionally include graphics, photos, audio files, video filesand/or other attachments as are supported in a MMS and/or an EnhancedMessaging Service (EMS). As used herein, “instant messaging” refers toboth telephony-based messages (e.g., messages sent using SMS or MMS) andInternet-based messages (e.g., messages sent using XMPP, SIMPLE, APNs,or IMPS).

In conjunction with RF circuitry 108, touch-sensitive display system112, display controller 156, contact module 130, graphics module 132,text input module 134, GPS module 135, map module 154, and music playermodule 146, workout support module 142 includes executable instructionsto create workouts (e.g., with time, distance, and/or calorie burninggoals); communicate with workout sensors (in sports devices and smartwatches); receive workout sensor data; calibrate sensors used to monitora workout; select and play music for a workout; and display, store andtransmit workout data.

In conjunction with touch-sensitive display system 112, displaycontroller 156, optical sensor(s) 164, optical sensor controller 158,contact module 130, graphics module 132, and image management module144, camera module 143 includes executable instructions to capture stillimages or video (including a video stream) and store them into memory102, modify characteristics of a still image or video, and/or delete astill image or video from memory 102.

In conjunction with touch-sensitive display system 112, displaycontroller 156, contact module 130, graphics module 132, text inputmodule 134, and camera module 143, image management module 144 includesexecutable instructions to arrange, modify (e.g., edit), or otherwisemanipulate, label, delete, present (e.g., in a digital slide show oralbum), and store still and/or video images.

In conjunction with RF circuitry 108, touch-sensitive display system112, display system controller 156, contact module 130, graphics module132, and text input module 134, browser module 147 includes executableinstructions to browse the Internet in accordance with userinstructions, including searching, linking to, receiving, and displayingweb pages or portions thereof, as well as attachments and other fileslinked to web pages.

In conjunction with RF circuitry 108, touch-sensitive display system112, display system controller 156, contact module 130, graphics module132, text input module 134, e-mail client module 140, and browser module147, calendar module 148 includes executable instructions to create,display, modify, and store calendars and data associated with calendars(e.g., calendar entries, to do lists, etc.) in accordance with userinstructions.

In conjunction with RF circuitry 108, touch-sensitive display system112, display system controller 156, contact module 130, graphics module132, text input module 134, and browser module 147, widget modules 149are mini-applications that are, optionally, downloaded and used by auser (e.g., weather widget 149-1, stocks widget 149-2, calculator widget149-3, alarm clock widget 149-4, and dictionary widget 149-5) or createdby the user (e.g., user-created widget 149-6). In some embodiments, awidget includes an HTML (Hypertext Markup Language) file, a CSS(Cascading Style Sheets) file, and a JavaScript file. In someembodiments, a widget includes an XML (Extensible Markup Language) fileand a JavaScript file (e.g., Yahoo! Widgets).

In conjunction with RF circuitry 108, touch-sensitive display system112, display system controller 156, contact module 130, graphics module132, text input module 134, and browser module 147, the widget creatormodule 150 includes executable instructions to create widgets (e.g.,turning a user-specified portion of a web page into a widget).

In conjunction with touch-sensitive display system 112, display systemcontroller 156, contact module 130, graphics module 132, and text inputmodule 134, search module 151 includes executable instructions to searchfor text, music, sound, image, video, and/or other files in memory 102that match one or more search criteria (e.g., one or more user-specifiedsearch terms) in accordance with user instructions.

In conjunction with touch-sensitive display system 112, display systemcontroller 156, contact module 130, graphics module 132, audio circuitry110, speaker 111, RF circuitry 108, and browser module 147, video andmusic player module 152 includes executable instructions that allow theuser to download and play back recorded music and other sound filesstored in one or more file formats, such as MP3 or AAC files, andexecutable instructions to display, present or otherwise play backvideos (e.g., on touch-sensitive display system 112, or on an externaldisplay connected wirelessly or via external port 124). In someembodiments, device 100 optionally includes the functionality of an MP3player, such as an iPod (trademark of Apple Inc.).

In conjunction with touch-sensitive display system 112, displaycontroller 156, contact module 130, graphics module 132, and text inputmodule 134, notes module 153 includes executable instructions to createand manage notes, to do lists, and the like in accordance with userinstructions.

In conjunction with RF circuitry 108, touch-sensitive display system112, display system controller 156, contact module 130, graphics module132, text input module 134, GPS module 135, and browser module 147, mapmodule 154 includes executable instructions to receive, display, modify,and store maps and data associated with maps (e.g., driving directions;data on stores and other points of interest at or near a particularlocation; and other location-based data) in accordance with userinstructions.

In conjunction with touch-sensitive display system 112, display systemcontroller 156, contact module 130, graphics module 132, audio circuitry110, speaker 111, RF circuitry 108, text input module 134, e-mail clientmodule 140, and browser module 147, online video module 155 includesexecutable instructions that allow the user to access, browse, receive(e.g., by streaming and/or download), play back (e.g., on touch screen112, or on an external display connected wirelessly or via external port124), send an e-mail with a link to a particular online video, andotherwise manage online videos in one or more file formats, such asH.264. In some embodiments, instant messaging module 141, rather thane-mail client module 140, is used to send a link to a particular onlinevideo.

Each of the above identified modules and applications correspond to aset of executable instructions for performing one or more functionsdescribed above and the methods described in this application (e.g., thecomputer-implemented methods and other information processing methodsdescribed herein). These modules (i.e., sets of instructions) need notbe implemented as separate software programs, procedures or modules, andthus various subsets of these modules are, optionally, combined orotherwise re-arranged in various embodiments. In some embodiments,memory 102 optionally stores a subset of the modules and data structuresidentified above. Furthermore, memory 102 optionally stores additionalmodules and data structures not described above.

In some embodiments, device 100 is a device where operation of apredefined set of functions on the device is performed exclusivelythrough a touch screen and/or a touchpad. By using a touch screen and/ora touchpad as the primary input control device for operation of device100, the number of physical input control devices (such as push buttons,dials, and the like) on device 100 is, optionally, reduced.

The predefined set of functions that are performed exclusively through atouch screen and/or a touchpad optionally include navigation betweenuser interfaces. In some embodiments, the touchpad, when touched by theuser, navigates device 100 to a main, home, or root menu from any userinterface that is displayed on device 100. In such embodiments, a “menubutton” is implemented using a touchpad. In some other embodiments, themenu button is a physical push button or other physical input controldevice instead of a touchpad.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments. In some embodiments,memory 102 (in FIG. 1A) or 370 (FIG. 3) includes event sorter 170 (e.g.,in operating system 126) and a respective application 136-1 (e.g., anyof the aforementioned applications 136, 137-155, 380-390).

Event sorter 170 receives event information and determines theapplication 136-1 and application view 191 of application 136-1 to whichto deliver the event information. Event sorter 170 includes eventmonitor 171 and event dispatcher module 174. In some embodiments,application 136-1 includes application internal state 192, whichindicates the current application view(s) displayed on touch-sensitivedisplay system 112 when the application is active or executing. In someembodiments, device/global internal state 157 is used by event sorter170 to determine which application(s) is (are) currently active, andapplication internal state 192 is used by event sorter 170 to determineapplication views 191 to which to deliver event information.

In some embodiments, application internal state 192 includes additionalinformation, such as one or more of: resume information to be used whenapplication 136-1 resumes execution, user interface state informationthat indicates information being displayed or that is ready for displayby application 136-1, a state queue for enabling the user to go back toa prior state or view of application 136-1, and a redo/undo queue ofprevious actions taken by the user.

Event monitor 171 receives event information from peripherals interface118. Event information includes information about a sub-event (e.g., auser touch on touch-sensitive display system 112, as part of amulti-touch gesture). Peripherals interface 118 transmits information itreceives from I/O subsystem 106 or a sensor, such as proximity sensor166, accelerometer(s) 167, gyroscope(s) 168, magnetometer(s) 169, and/ormicrophone 113 (through audio circuitry 110). Information thatperipherals interface 118 receives from I/O subsystem 106 includesinformation from touch-sensitive display system 112 or a touch-sensitivesurface.

In some embodiments, event monitor 171 sends requests to the peripheralsinterface 118 at predetermined intervals. In response, peripheralsinterface 118 transmits event information. In other embodiments,peripheral interface 118 transmits event information only when there isa significant event (e.g., receiving an input above a predeterminednoise threshold and/or for more than a predetermined duration).

In some embodiments, event sorter 170 also includes a hit viewdetermination module 172 and/or an active event recognizer determinationmodule 173.

Hit view determination module 172 provides software procedures fordetermining where a sub-event has taken place within one or more views,when touch-sensitive display system 112 displays more than one view.Views are made up of controls and other elements that a user can see onthe display.

Another aspect of the user interface associated with an application is aset of views, sometimes herein called application views or userinterface windows, in which information is displayed and touch-basedgestures occur. The application views (of a respective application) inwhich a touch is detected optionally correspond to programmatic levelswithin a programmatic or view hierarchy of the application. For example,the lowest level view in which a touch is detected is, optionally,called the hit view, and the set of events that are recognized as properinputs are, optionally, determined based, at least in part, on the hitview of the initial touch that begins a touch-based gesture.

Hit view determination module 172 receives information related tosub-events of a touch-based gesture. When an application has multipleviews organized in a hierarchy, hit view determination module 172identifies a hit view as the lowest view in the hierarchy which shouldhandle the sub-event. In most circumstances, the hit view is the lowestlevel view in which an initiating sub-event occurs (i.e., the firstsub-event in the sequence of sub-events that form an event or potentialevent). Once the hit view is identified by the hit view determinationmodule, the hit view typically receives all sub-events related to thesame touch or input source for which it was identified as the hit view.

Active event recognizer determination module 173 determines which viewor views within a view hierarchy should receive a particular sequence ofsub-events. In some embodiments, active event recognizer determinationmodule 173 determines that only the hit view should receive a particularsequence of sub-events. In other embodiments, active event recognizerdetermination module 173 determines that all views that include thephysical location of a sub-event are actively involved views, andtherefore determines that all actively involved views should receive aparticular sequence of sub-events. In other embodiments, even if touchsub-events were entirely confined to the area associated with oneparticular view, views higher in the hierarchy would still remain asactively involved views.

Event dispatcher module 174 dispatches the event information to an eventrecognizer (e.g., event recognizer 180). In embodiments including activeevent recognizer determination module 173, event dispatcher module 174delivers the event information to an event recognizer determined byactive event recognizer determination module 173. In some embodiments,event dispatcher module 174 stores in an event queue the eventinformation, which is retrieved by a respective event receiver module182.

In some embodiments, operating system 126 includes event sorter 170.Alternatively, application 136-1 includes event sorter 170. In yet otherembodiments, event sorter 170 is a stand-alone module, or a part ofanother module stored in memory 102, such as contact/motion module 130.

In some embodiments, application 136-1 includes a plurality of eventhandlers 190 and one or more application views 191, each of whichincludes instructions for handling touch events that occur within arespective view of the application's user interface. Each applicationview 191 of the application 136-1 includes one or more event recognizers180. Typically, a respective application view 191 includes a pluralityof event recognizers 180. In other embodiments, one or more of eventrecognizers 180 are part of a separate module, such as a user interfacekit (not shown) or a higher level object from which application 136-1inherits methods and other properties. In some embodiments, a respectiveevent handler 190 includes one or more of: data updater 176, objectupdater 177, GUI updater 178, and/or event data 179 received from eventsorter 170. Event handler 190 optionally utilizes or calls data updater176, object updater 177 or GUI updater 178 to update the applicationinternal state 192. Alternatively, one or more of the application views191 includes one or more respective event handlers 190. Also, in someembodiments, one or more of data updater 176, object updater 177, andGUI updater 178 are included in a respective application view 191.

As used herein, a force event refers to a device-generated signal ordevice-generated data (e.g., a signal or a data object generated orupdated by device 100) to indicate status or a change in status of atouch input, such as beginning (e.g., satisfying a minimum forceintensity threshold), changing intensity (e.g., increasing or decreasingintensity of the touch input), or changing intensity status (e.g., hardpress to exceed a high intensity threshold or release the touch input sothat the intensity falls below the high intensity threshold) of thetouch input. Although force events are associated with physical touches(e.g., touches with a finger and/or a stylus) on the touch-sensitivesurface, the force events, as described herein, are distinct from thephysical touches.

A respective event recognizer 180 receives event information (e.g.,event data 179) from event sorter 170, and identifies an event from theevent information. Event recognizer 180 includes event receiver 182 andevent comparator 184. In some embodiments, event recognizer 180 alsoincludes at least a subset of: metadata 183, and event deliveryinstructions 188 (which optionally include sub-event deliveryinstructions).

Event receiver 182 receives event information from event sorter 170. Theevent information includes information about a sub-event, for example, atouch or a touch movement. Depending on the sub-event, the eventinformation also includes additional information, such as location ofthe sub-event. When the sub-event concerns motion of a touch, the eventinformation optionally also includes speed and direction of thesub-event. In some embodiments, events include rotation of the devicefrom one orientation to another (e.g., from a portrait orientation to alandscape orientation, or vice versa), and the event informationincludes corresponding information about the current orientation (alsocalled device attitude) of the device.

Event comparator 184 compares the event information to predefined eventor sub-event definitions and, based on the comparison, determines anevent or sub-event, or determines or updates the state of an event orsub-event. In some embodiments, event comparator 184 includes eventdefinitions 186. Event definitions 186 contain definitions of events(e.g., predefined sequences of sub-events), for example, event 1(187-1), event 2 (187-2), and others. In some embodiments, sub-events inan event 187 include, for example, touch begin, touch end, touchmovement, touch cancellation, and multiple touching. In one example, thedefinition for event 1 (187-1) is a double tap on a displayed object.The double tap, for example, comprises a first touch (touch begin) onthe displayed object for a predetermined phase, a first lift-off (touchend) for a predetermined phase, a second touch (touch begin) on thedisplayed object for a predetermined phase, and a second lift-off (touchend) for a predetermined phase. In another example, the definition forevent 2 (187-2) is a dragging on a displayed object. The dragging, forexample, comprises a touch (or contact) on the displayed object for apredetermined phase, a movement of the touch across touch-sensitivedisplay system 112, and lift-off of the touch (touch end). In someembodiments, the event also includes information for one or moreassociated event handlers 190.

In some embodiments, event definition 187 includes a definition of anevent for a respective user-interface object. In some embodiments, eventcomparator 184 performs a hit test to determine which user-interfaceobject is associated with a sub-event. For example, in an applicationview in which three user-interface objects are displayed ontouch-sensitive display system 112, when a touch is detected ontouch-sensitive display system 112, event comparator 184 performs a hittest to determine which of the three user-interface objects isassociated with the touch (sub-event). If each displayed object isassociated with a respective event handler 190, the event comparatoruses the result of the hit test to determine which event handler 190should be activated. For example, event comparator 184 selects an eventhandler associated with the sub-event and the object triggering the hittest.

In some embodiments, the definition for a respective event 187 alsoincludes delayed actions that delay delivery of the event informationuntil after it has been determined whether the sequence of sub-eventsdoes or does not correspond to the event recognizer's event type.

When a respective event recognizer 180 determines that the series ofsub-events do not match any of the events in event definitions 186, therespective event recognizer 180 enters an event impossible, eventfailed, or event ended state, after which it disregards subsequentsub-events of the touch-based gesture. In this situation, other eventrecognizers, if any, that remain active for the hit view continue totrack and process sub-events of an ongoing touch-based gesture.

In some embodiments, a respective event recognizer 180 includes metadata183 with configurable properties, flags, and/or lists that indicate howthe event delivery system should perform sub-event delivery to activelyinvolved event recognizers. In some embodiments, metadata 183 includesconfigurable properties, flags, and/or lists that indicate how eventrecognizers interact, or are enabled to interact, with one another. Insome embodiments, metadata 183 includes configurable properties, flags,and/or lists that indicate whether sub-events are delivered to varyinglevels in the view or programmatic hierarchy.

In some embodiments, a respective event recognizer 180 activates eventhandler 190 associated with an event when one or more particularsub-events of an event are recognized. In some embodiments, a respectiveevent recognizer 180 delivers event information associated with theevent to event handler 190. Activating an event handler 190 is distinctfrom sending (and deferred sending) sub-events to a respective hit view.In some embodiments, event recognizer 180 throws a flag associated withthe recognized event, and event handler 190 associated with the flagcatches the flag and performs a predefined process.

In some embodiments, event delivery instructions 188 include sub-eventdelivery instructions that deliver event information about a sub-eventwithout activating an event handler. Instead, the sub-event deliveryinstructions deliver event information to event handlers associated withthe series of sub-events or to actively involved views. Event handlersassociated with the series of sub-events or with actively involved viewsreceive the event information and perform a predetermined process.

In some embodiments, data updater 176 creates and updates data used inapplication 136-1. For example, data updater 176 updates the telephonenumber used in contacts module 137, or stores a video file used in videoplayer module 145. In some embodiments, object updater 177 creates andupdates objects used in application 136-1. For example, object updater177 creates a new user-interface object or updates the position of auser-interface object. GUI updater 178 updates the GUI. For example, GUIupdater 178 prepares display information and sends it to graphics module132 for display on a touch-sensitive display.

In some embodiments, event handler(s) 190 includes or has access to dataupdater 176, object updater 177, and GUI updater 178. In someembodiments, data updater 176, object updater 177, and GUI updater 178are included in a single module of a respective application 136-1 orapplication view 191. In other embodiments, they are included in two ormore software modules.

It shall be understood that the foregoing discussion regarding eventhandling of user touches on touch-sensitive displays also applies toother forms of user inputs to operate multifunction devices 100 withinput-devices, not all of which are initiated on touch screens. Forexample, mouse movement and mouse button presses, optionally coordinatedwith single or multiple keyboard presses or holds; contact movementssuch as taps, drags, scrolls, etc., on touch-pads; pen stylus inputs;movement of the device; oral instructions; detected eye movements;biometric inputs; and/or any combination thereof are optionally utilizedas inputs corresponding to sub-events which define an event to berecognized.

FIG. 1C is a block diagram illustrating transfer of event object 194 inaccordance with some embodiments.

As described above with respect to FIG. 1A, contact/motion module 130determines status and/or a change in the status of a touch input. Insome embodiments, the device generates signal or data (e.g., in the formof a data object) to transfer the determined status and/or thedetermined change in the status of a touch input to one or more softwarecomponents. In some embodiments, the data object is called an eventobject (e.g., event object 194). An event object includes data thatrepresents the status of a corresponding touch input. In someembodiments, event object 194 is a mouse event object (because the touchinput is equivalent to an input by a mouse). For example, in suchembodiments, a touch input moving across a touch-sensitive surfacecorresponds to a mouse movement (e.g., a mouse moved event). In someother embodiments, event object 194 is a touch event object that isdistinct from a mouse event object. In some embodiments, the touch eventobject includes data that represents touch-specific properties of acorresponding touch input (e.g., a number of concurrent touches, anorientation of a finger contact or a stylus, etc.). In some embodiments,event object 194 is a force event object that is distinct from a mouseevent object (or a touch event object). In some embodiments, the forceevent object includes data that represents force event specificproperties of a corresponding touch input (e.g., an intensity applied bythe touch input, a stage/phase of the touch input, etc.). In someembodiments, the event object includes any combination of suchproperties (e.g., mouse event specific properties, touch event specificproperties, and force event specific properties).

In some embodiments, contact/motion module 130 sends event object 194 toone or more applications (e.g., applications 136 in FIG. 1A). In someembodiments, contact/motion module 130 sends event object 194 to webengine module 175. In some embodiments, event object 194 is sentdirectly to the destination (e.g., a software component, such asapplications 136 and/or web engine module 175). In some embodiments,event object 194 is sent by posting event object 194 for retrieval byapplication 136 and/or web engine module 175.

In some embodiments, the device uses web engine module 175 to processinstructions in web page 185 based on information in event object 194.For example, in accordance with a determination that force (orintensity) of a touch input indicated in event object 194 meetspredefined criteria, the device uses web engine module 175 to processinstructions in web page 185 that corresponds to the force of the touchinput indicated in event object 194.

In some embodiments, event object 194 includes force information. Insome embodiments, a mouse event object includes force information (e.g.,raw or normalized force applied by the touch input). In someembodiments, a touch event object includes force information. In someembodiments, a force event object includes force information.

FIG. 2 illustrates a portable multifunction device 100 having a touchscreen (e.g., touch-sensitive display system 112, FIG. 1A) in accordancewith some embodiments. The touch screen optionally displays one or moregraphics within user interface (UI) 200. In these embodiments, as wellas others described below, a user is enabled to select one or more ofthe graphics by making a gesture on the graphics, for example, with oneor more fingers 202 (not drawn to scale in the figure) or one or morestyluses 203 (not drawn to scale in the figure). In some embodiments,selection of one or more graphics occurs when the user breaks contactwith the one or more graphics. In some embodiments, the gestureoptionally includes one or more taps, one or more swipes (from left toright, right to left, upward and/or downward) and/or a rolling of afinger (from right to left, left to right, upward and/or downward) thathas made contact with device 100. In some implementations orcircumstances, inadvertent contact with a graphic does not select thegraphic. For example, a swipe gesture that sweeps over an applicationicon optionally does not select the corresponding application when thegesture corresponding to selection is a tap.

Device 100 optionally also includes one or more physical buttons, suchas “home” or menu button 204. As described previously, menu button 204is, optionally, used to navigate to any application 136 in a set ofapplications that are, optionally executed on device 100. Alternatively,in some embodiments, the menu button is implemented as a soft key in aGUI displayed on the touch-screen display.

In some embodiments, device 100 includes the touch-screen display, menubutton 204, push button 206 for powering the device on/off and lockingthe device, volume adjustment button(s) 208, Subscriber Identity Module(SIM) card slot 210, head set jack 212, and docking/charging externalport 124. Push button 206 is, optionally, used to turn the power on/offon the device by depressing the button and holding the button in thedepressed state for a predefined time interval; to lock the device bydepressing the button and releasing the button before the predefinedtime interval has elapsed; and/or to unlock the device or initiate anunlock process. In some embodiments, device 100 also accepts verbalinput for activation or deactivation of some functions throughmicrophone 113. Device 100 also, optionally, includes one or morecontact intensity sensors 165 for detecting intensity of contacts ontouch-sensitive display system 112 and/or one or more tactile outputgenerators 163 for generating tactile outputs for a user of device 100.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments. Device 300 need not be portable. In some embodiments,device 300 is a laptop computer, a desktop computer, a tablet computer,a multimedia player device, a navigation device, an educational device(such as a child's learning toy), a gaming system, or a control device(e.g., a home or industrial controller). Device 300 typically includesone or more processing units (CPU's) 310, one or more network or othercommunications interfaces 360, memory 370, and one or more communicationbuses 320 for interconnecting these components. Communication buses 320optionally include circuitry (sometimes called a chipset) thatinterconnects and controls communications between system components.Device 300 includes input/output (I/O) interface 330 comprising display340, which is typically a touch-screen display. I/O interface 330 alsooptionally includes a keyboard and/or mouse (or other pointing device)350 and touchpad 355, tactile output generator 357 for generatingtactile outputs on device 300 (e.g., similar to tactile outputgenerator(s) 163 described above with reference to FIG. 1A), sensors 359(e.g., touch-sensitive, optical, contact intensity, proximity,acceleration, attitude, and/or magnetic sensors similar to sensors 112,164, 165, 166, 167, 168, and 169 described above with reference to FIG.1A). Memory 370 includes high-speed random access memory, such as DRAM,SRAM, DDR RAM or other random access solid state memory devices; andoptionally includes non-volatile memory, such as one or more magneticdisk storage devices, optical disk storage devices, flash memorydevices, or other non-volatile solid state storage devices. Memory 370optionally includes one or more storage devices remotely located fromCPU(s) 310. In some embodiments, memory 370 stores programs, modules,and data structures analogous to the programs, modules, and datastructures stored in memory 102 of portable multifunction device 100(FIG. 1A), or a subset thereof. Furthermore, memory 370 optionallystores additional programs, modules, and data structures not present inmemory 102 of portable multifunction device 100. For example, memory 370of device 300 optionally stores drawing module 380, presentation module382, word processing module 384, website creation module 386, diskauthoring module 388, and/or spreadsheet module 390, while memory 102 ofportable multifunction device 100 (FIG. 1A) optionally does not storethese modules.

Each of the above identified elements in FIG. 3 is, optionally, storedin one or more of the previously mentioned memory devices. Each of theabove identified modules corresponds to a set of instructions forperforming a function described above. The above identified modules orprograms (i.e., sets of instructions) need not be implemented asseparate software programs, procedures or modules, and thus varioussubsets of these modules are, optionally, combined or otherwisere-arranged in various embodiments. In some embodiments, memory 370optionally stores a subset of the modules and data structures identifiedabove. Furthermore, memory 370 optionally stores additional modules anddata structures not described above.

FIG. 4 is a block diagram of an exemplary electronic stylus 203 inaccordance with some embodiments. Electronic stylus 203 is sometimessimply called a stylus. Stylus 203 includes memory 402 (which optionallyincludes one or more computer readable storage mediums), memorycontroller 422, one or more processing units (CPUs) 420, peripheralsinterface 418, RF circuitry 408, input/output (I/O) subsystem 406, andother input or control devices 416. Stylus 203 optionally includesexternal port 424 and one or more optical sensors 464. Stylus 203optionally includes one or more intensity sensors 465 for detectingintensity of contacts of stylus 203 on device 100 (e.g., when stylus 203is used with a touch-sensitive surface such as touch-sensitive displaysystem 112 of device 100) or on other surfaces (e.g., a desk surface).Stylus 203 optionally includes one or more tactile output generators 463for generating tactile outputs on stylus 203. These componentsoptionally communicate over one or more communication buses or signallines 403.

In some embodiments, the term “tactile output,” discussed above, refersto physical displacement of an accessory (e.g., stylus 203) of a device(e.g., device 100) relative to a previous position of the accessory,physical displacement of a component of an accessory relative to anothercomponent of the accessory, or displacement of the component relative toa center of mass of the accessory that will be detected by a user withthe user's sense of touch. For example, in situations where theaccessory or the component of the accessory is in contact with a surfaceof a user that is sensitive to touch (e.g., a finger, palm, or otherpart of a user's hand), the tactile output generated by the physicaldisplacement will be interpreted by the user as a tactile sensationcorresponding to a perceived change in physical characteristics of theaccessory or the component of the accessory. For example, movement of acomponent (e.g., the housing of stylus 203) is, optionally, interpretedby the user as a “click” of a physical actuator button. In some cases, auser will feel a tactile sensation such as a “click” even when there isno movement of a physical actuator button associated with the stylusthat is physically pressed (e.g., displaced) by the user's movements.While such interpretations of touch by a user will be subject to theindividualized sensory perceptions of the user, there are many sensoryperceptions of touch that are common to a large majority of users. Thus,when a tactile output is described as corresponding to a particularsensory perception of a user (e.g., a “click,”), unless otherwisestated, the generated tactile output corresponds to physicaldisplacement of the device or a component thereof that will generate thedescribed sensory perception for a typical (or average) user.

It should be appreciated that stylus 203 is only one example of anelectronic stylus, and that stylus 203 optionally has more or fewercomponents than shown, optionally combines two or more components, oroptionally has a different configuration or arrangement of thecomponents. The various components shown in FIG. 4 are implemented inhardware, software, firmware, or a combination thereof, including one ormore signal processing and/or application specific integrated circuits.

Memory 402 optionally includes high-speed random access memory andoptionally also includes non-volatile memory, such as one or more flashmemory devices, or other non-volatile solid-state memory devices. Accessto memory 402 by other components of stylus 203, such as CPU(s) 420 andthe peripherals interface 418, is, optionally, controlled by memorycontroller 422.

Peripherals interface 418 can be used to couple input and outputperipherals of the stylus to CPU(s) 420 and memory 402. The one or moreprocessors 420 run or execute various software programs and/or sets ofinstructions stored in memory 402 to perform various functions forstylus 203 and to process data.

In some embodiments, peripherals interface 418, CPU(s) 420, and memorycontroller 422 are, optionally, implemented on a single chip, such aschip 404. In some other embodiments, they are, optionally, implementedon separate chips.

RF (radio frequency) circuitry 408 receives and sends RF signals, alsocalled electromagnetic signals. RF circuitry 408 converts electricalsignals to/from electromagnetic signals and communicates with device 100or 300, communications networks, and/or other communications devices viathe electromagnetic signals. RF circuitry 408 optionally includeswell-known circuitry for performing these functions, including but notlimited to an antenna system, an RF transceiver, one or more amplifiers,a tuner, one or more oscillators, a digital signal processor, a CODECchipset, a subscriber identity module (SIM) card, memory, and so forth.RF circuitry 408 optionally communicates with networks, such as theInternet, also referred to as the World Wide Web (WWW), an intranetand/or a wireless network, such as a cellular telephone network, awireless local area network (LAN) and/or a metropolitan area network(MAN), and other devices by wireless communication. The wirelesscommunication optionally uses any of a plurality of communicationsstandards, protocols and technologies, including but not limited toGlobal System for Mobile Communications (GSM), Enhanced Data GSMEnvironment (EDGE), high-speed downlink packet access (HSDPA),high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO),HSPA, HSPA+, Dual-Cell HSPA (DC-HSPDA), long term evolution (LTE), nearfield communication (NFC), wideband code division multiple access(W-CDMA), code division multiple access (CDMA), time division multipleaccess (TDMA), Bluetooth, Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.11a,IEEE 802.11ac, IEEE 802.11ax, IEEE 802.11b, IEEE 802.11g and/or IEEE802.11n), voice over Internet Protocol (VoIP), Wi-MAX, a protocol fore-mail (e.g., Internet message access protocol (IMAP) and/or post officeprotocol (POP)), instant messaging (e.g., extensible messaging andpresence protocol (XMPP), Session Initiation Protocol for InstantMessaging and Presence Leveraging Extensions (SIMPLE), Instant Messagingand Presence Service (IMPS)), and/or Short Message Service (SMS), or anyother suitable communication protocol, including communication protocolsnot yet developed as of the filing date of this document.

I/O subsystem 406 couples input/output peripherals on stylus 203, suchas other input or control devices 416, with peripherals interface 418.I/O subsystem 406 optionally includes optical sensor controller 458,intensity sensor controller 459, haptic feedback controller 461, and oneor more input controllers 460 for other input or control devices. Theone or more input controllers 460 receive/send electrical signalsfrom/to other input or control devices 416. The other input or controldevices 416 optionally include physical buttons (e.g., push buttons,rocker buttons, etc.), dials, slider switches, click wheels, and soforth. In some alternate embodiments, input controller(s) 460 are,optionally, coupled with any (or none) of the following: an infraredport and/or a USB port.

Stylus 203 also includes power system 462 for powering the variouscomponents. Power system 462 optionally includes a power managementsystem, one or more power sources (e.g., battery, alternating current(AC)), a recharging system, a power failure detection circuit, a powerconverter or inverter, a power status indicator (e.g., a light-emittingdiode (LED)) and any other components associated with the generation,management and distribution of power in portable devices and/or portableaccessories.

Stylus 203 optionally also includes one or more optical sensors 464.FIG. 4 shows an optical sensor coupled with optical sensor controller458 in I/O subsystem 406. Optical sensor(s) 464 optionally includecharge-coupled device (CCD) or complementary metal-oxide semiconductor(CMOS) phototransistors. Optical sensor(s) 464 receive light from theenvironment, projected through one or more lens, and converts the lightto data representing an image.

Stylus 203 optionally also includes one or more contact intensitysensors 465. FIG. 4 shows a contact intensity sensor coupled withintensity sensor controller 459 in I/O subsystem 406. Contact intensitysensor(s) 465 optionally include one or more piezoresistive straingauges, capacitive force sensors, electric force sensors, piezoelectricforce sensors, optical force sensors, capacitive touch-sensitivesurfaces, or other intensity sensors (e.g., sensors used to measure theforce (or pressure) of a contact on a surface). Contact intensitysensor(s) 465 receive contact intensity information (e.g., pressureinformation or a proxy for pressure information) from the environment.In some embodiments, at least one contact intensity sensor is collocatedwith, or proximate to, a tip of stylus 203.

Stylus 203 optionally also includes one or more proximity sensors 466.FIG. 4 shows proximity sensor 466 coupled with peripherals interface418. Alternately, proximity sensor 466 is coupled with input controller460 in I/O subsystem 406. In some embodiments, the proximity sensordetermines proximity of stylus 203 to an electronic device (e.g., device100).

Stylus 203 optionally also includes one or more tactile outputgenerators 463. FIG. 4 shows a tactile output generator coupled withhaptic feedback controller 461 in I/O subsystem 406. Tactile outputgenerator(s) 463 optionally include one or more electroacoustic devicessuch as speakers or other audio components and/or electromechanicaldevices that convert energy into linear motion such as a motor,solenoid, electroactive polymer, piezoelectric actuator, electrostaticactuator, or other tactile output generating component (e.g., acomponent that converts electrical signals into tactile outputs on thedevice). Tactile output generator(s) 463 receive tactile feedbackgeneration instructions from haptic feedback module 433 and generatestactile outputs on stylus 203 that are capable of being sensed by a userof stylus 203. In some embodiments, at least one tactile outputgenerator is collocated with, or proximate to, a length (e.g., a body ora housing) of stylus 203 and, optionally, generates a tactile output bymoving stylus 203 vertically (e.g., in a direction parallel to thelength of stylus 203) or laterally (e.g., in a direction normal to thelength of stylus 203).

Stylus 203 optionally also includes one or more accelerometers 467,gyroscopes 468, and/or magnetometers 470 (e.g., as part of an inertialmeasurement unit (IMU)) for obtaining information concerning thelocation and positional state of stylus 203. FIG. 4 shows sensors 467,469, and 470 coupled with peripherals interface 418. Alternately,sensors 467, 469, and 470 are, optionally, coupled with an inputcontroller 460 in I/O subsystem 406. Stylus 203 optionally includes aGPS (or GLONASS or other global navigation system) receiver (not shown)for obtaining information concerning the location of stylus 203.

In some embodiments, the software components stored in memory 402include operating system 426, communication module (or set ofinstructions) 428, contact/motion module (or set of instructions) 430,position module (or set of instructions) 431, and Global PositioningSystem (GPS) module (or set of instructions) 435. Furthermore, in someembodiments, memory 402 stores device/global internal state 457, asshown in FIG. 4. Device/global internal state 457 includes one or moreof: sensor state, including information obtained from the stylus'svarious sensors and other input or control devices 416; positionalstate, including information regarding the stylus's position (e.g.,position, orientation, tilt, roll and/or distance, as shown in FIGS. 5Aand 5B) relative to a device (e.g., device 100); and locationinformation concerning the stylus's location (e.g., determined by GPSmodule 435).

Operating system 426 (e.g., iOS, Darwin, RTXC, LINUX, UNIX, OS X,WINDOWS, or an embedded operating system such as VxWorks) includesvarious software components and/or drivers for controlling and managinggeneral system tasks (e.g., memory management, power management, etc.)and facilitates communication between various hardware and softwarecomponents.

Communication module 428 optionally facilitates communication with otherdevices over one or more external ports 424 and also includes varioussoftware components for handling data received by RF circuitry 408and/or external port 424. External port 424 (e.g., Universal Serial Bus(USB), FIREWIRE, etc.) is adapted for coupling directly to other devicesor indirectly over a network (e.g., the Internet, wireless LAN, etc.).In some embodiments, the external port is a Lightning connector that isthe same as, or similar to and/or compatible with the Lightningconnector used in some iPhone®, iPod Touch®, and iPad® devices fromApple Inc. of Cupertino, Calif.

Contact/motion module 430 optionally detects contact with stylus 203 andother touch-sensitive devices of stylus 203 (e.g., buttons or othertouch-sensitive components of stylus 203). Contact/motion module 430includes software components for performing various operations relatedto detection of contact (e.g., detection of a tip of the stylus with atouch-sensitive display, such as touch screen 112 of device 100, or withanother surface, such as a desk surface), such as determining if contacthas occurred (e.g., detecting a touch-down event), determining anintensity of the contact (e.g., the force or pressure of the contact ora substitute for the force or pressure of the contact), determining ifthere is movement of the contact and tracking the movement (e.g., acrosstouch screen 112 of device 100), and determining if the contact hasceased (e.g., detecting a lift-off event or a break in contact). In someembodiments, contact/motion module 430 receives contact data from I/Osubsystem 406. Determining movement of the point of contact, which isrepresented by a series of contact data, optionally includes determiningspeed (magnitude), velocity (magnitude and direction), and/or anacceleration (a change in magnitude and/or direction) of the point ofcontact. As noted above, in some embodiments, one or more of theseoperations related to detection of contact are performed by the deviceusing contact/motion module 130 (in addition to or in place of thestylus using contact/motion module 430).

Contact/motion module 430 optionally detects a gesture input by stylus203. Different gestures with stylus 203 have different contact patterns(e.g., different motions, timings, and/or intensities of detectedcontacts). Thus, a gesture is, optionally, detected by detecting aparticular contact pattern. For example, detecting a single tap gestureincludes detecting a touch-down event followed by detecting a lift-offevent at the same position (or substantially the same position) as thetouch-down event (e.g., at the position of an icon). As another example,detecting a swipe gesture includes detecting a touch-down event followedby detecting one or more stylus-dragging events, and subsequentlyfollowed by detecting a lift-off event. As noted above, in someembodiments, gesture detection is performed by the device usingcontact/motion module 130 (in addition to or in place of the stylususing contact/motion module 430).

Position module 431, in conjunction with accelerometers 467, gyroscopes468, and/or magnetometers 469, optionally detects positional informationconcerning the stylus, such as the stylus's attitude (roll, pitch,and/or yaw) in a particular frame of reference. Position module 431, inconjunction with accelerometers 467, gyroscopes 468, and/ormagnetometers 469, optionally detects stylus movement gestures, such asflicks, taps, and rolls of the stylus. Position module 431 includessoftware components for performing various operations related todetecting the position of the stylus and detecting changes to theposition of the stylus in a particular frame of reference. In someembodiments, position module 431 detects the positional state of thestylus relative to the device and detects changes to the positionalstate of the stylus relative to the device. As noted above, in someembodiments, device 100 or 300 determines the positional state of thestylus relative to the device and changes to the positional state of thestylus using position module 131 (in addition to or in place of thestylus using position module 431).

Haptic feedback module 433 includes various software components forgenerating instructions used by tactile output generator(s) 463 toproduce tactile outputs at one or more locations on stylus 203 inresponse to user interactions with stylus 203.

GPS module 435 determines the location of the stylus and provides thisinformation for use in various applications (e.g., to applications thatprovide location-based services such as an application to find missingdevices and/or accessories).

Each of the above identified modules and applications correspond to aset of executable instructions for performing one or more functionsdescribed above and the methods described in this application (e.g., thecomputer-implemented methods and other information processing methodsdescribed herein). These modules (i.e., sets of instructions) need notbe implemented as separate software programs, procedures or modules, andthus various subsets of these modules are, optionally, combined orotherwise re-arranged in various embodiments. In some embodiments,memory 402 optionally stores a subset of the modules and data structuresidentified above. Furthermore, memory 402 optionally stores additionalmodules and data structures not described above.

FIGS. 5A-5B illustrate a positional state of stylus 203 relative to atouch-sensitive surface (e.g., touch screen 112 of device 100) inaccordance with some embodiments. In some embodiments, the positionalstate of stylus 203 corresponds to (or indicates): a position of aprojection of a tip (or other representative portion) of the stylus onthe touch-sensitive surface (e.g., (x,y) position 504, FIG. 5A), anorientation of the stylus relative to the touch-sensitive surface (e.g.,orientation 506, FIG. 5A), a tilt of the stylus relative to thetouch-sensitive surface (e.g., tilt 512, FIG. 5B), and/or a distance ofthe stylus relative to the touch-sensitive surface (e.g., distance 514,FIG. 5B). In some embodiments, the positional state of stylus 203corresponds to (or indicates) a pitch, yaw, and/or roll of the stylus(e.g., an attitude of the stylus relative to a particular frame ofreference, such as a touch-sensitive surface (e.g., touch screen 112) orthe ground). In some embodiments, the positional state includes a set ofpositional parameters (e.g., one or more positional parameters). In someembodiments, the positional state is detected in accordance with one ormore measurements from stylus 203 that are sent to an electronic device(e.g., device 100). For example, the stylus measures the tilt (e.g.,tilt 512, FIG. 5B) and/or the orientation (e.g., orientation 506, FIG.5A) of the stylus and sends the measurement to device 100. In someembodiments, the positional state is detected in accordance with rawoutput, from one or more electrodes in the stylus, that is sensed by atouch-sensitive surface (e.g., touch screen 112 of device 100) insteadof, or in combination with positional state detected in accordance withone or more measurements from stylus 203. For example, thetouch-sensitive surface receives raw output from one or more electrodesin the stylus and calculates the tilt and/or the orientation of thestylus based on the raw output (optionally, in conjunction withpositional state information provided by the stylus based on sensormeasurements generated by the stylus).

FIG. 5A illustrates stylus 203 relative to a touch-sensitive surface(e.g., touch screen 112 of device 100) from a viewpoint directly abovethe touch-sensitive surface, in accordance with some embodiments. InFIG. 5A, z axis 594 points out of the page (i.e., in a direction normalto a plane of touch screen 112), x axis 590 is parallel to a first edge(e.g., a length) of touch screen 112, y axis 592 is parallel to a secondedge (e.g., a width) of touch screen 112, and y axis 592 isperpendicular to x axis 590.

FIG. 5A illustrates the tip of stylus 203 at (x,y) position 504. In someembodiments, the tip of stylus 203 is a terminus of the stylusconfigured for determining proximity of the stylus to a touch-sensitivesurface (e.g., touch screen 112). In some embodiments, the projection ofthe tip of the stylus on the touch-sensitive surface is an orthogonalprojection. In other words, the projection of the tip of the stylus onthe touch-sensitive surface is a point at the end of a line from thestylus tip to the touch-sensitive surface that is normal to a surface ofthe touch-sensitive surface (e.g., (x,y) position 504 at which the tipof the stylus would touch the touch-sensitive surface if the stylus weremoved directly along a path normal to the touch-sensitive surface). Insome embodiments, the (x,y) position at the lower left corner of touchscreen 112 is position (0,0) (e.g., (0,0) position 502) and other (x,y)positions on touch screen 112 are relative to the lower left corner oftouch screen 112. Alternatively, in some embodiments, the (0,0) positionis located at another position of touch screen 112 (e.g., in the centerof touch screen 112) and other (x,y) positions are relative to the (0,0)position of touch screen 112.

Further, FIG. 5A illustrates stylus 203 with orientation 506. In someembodiments, orientation 506 is an orientation of a projection of stylus203 onto touch screen 112 (e.g., an orthogonal projection of a length ofstylus 203 or a line corresponding to the line between the projection oftwo different points of stylus 203 onto touch screen 112). In someembodiments, orientation 506 is relative to at least one axis in a planeparallel to touch screen 112. In some embodiments, orientation 506 isrelative to a single axis in a plane parallel to touch screen 112 (e.g.,axis 508, with a clockwise rotation angle from axis 508 ranging from 0degrees to 360 degrees, as shown in FIG. 5A). Alternatively, in someembodiments, orientation 506 is relative to a pair of axes in a planeparallel to touch screen 112 (e.g., x axis 590 and y axis 592, as shownin FIG. 5A, or a pair of axes associated with an application displayedon touch screen 112).

In some embodiments, an indication (e.g., indication 516) is displayedon a touch-sensitive display (e.g., touch screen 112 of device 100). Insome embodiments, indication 516 shows where the stylus will touch (ormark) the touch-sensitive display before the stylus touches thetouch-sensitive display. In some embodiments, indication 516 is aportion of a mark that is being drawn on the touch-sensitive display. Insome embodiments, indication 516 is separate from a mark that is beingdrawn on the touch-sensitive display and corresponds to a virtual “pentip” or other element that indicates where a mark will be drawn on thetouch-sensitive display.

In some embodiments, indication 516 is displayed in accordance with thepositional state of stylus 203. For example, in some circumstances,indication 516 is displaced from (x,y) position 504 (as shown in FIGS.5A and 5B), and in other circumstances, indication 516 is not displacedfrom (x,y) position 504 (e.g., indication 516 is displayed at or near(x,y) position 504 when tilt 512 is zero degrees). In some embodiments,indication 516 is displayed, in accordance with the positional state ofthe stylus, with varying color, size (or radius or area), opacity,and/or other characteristics. In some embodiments, the displayedindication accounts for thickness of a glass layer on thetouch-sensitive display, so as to carry through the indication “onto thepixels” of the touch-sensitive display, rather than displaying theindication “on the glass” that covers the pixels.

FIG. 5B illustrates stylus 203 relative to a touch-sensitive surface(e.g., touch screen 112 of device 100) from a side viewpoint of thetouch-sensitive surface, in accordance with some embodiments. In FIG.5B, z axis 594 points in a direction normal to the plane of touch screen112, x axis 590 is parallel to a first edge (e.g., a length) of touchscreen 112, y axis 592 is parallel to a second edge (e.g., a width) oftouch screen 112, and y axis 592 is perpendicular to x axis 590.

FIG. 5B illustrates stylus 203 with tilt 512. In some embodiments, tilt512 is an angle relative to a normal (e.g., normal 510) to a surface ofthe touch-sensitive surface (also called simply the normal to thetouch-sensitive surface). As shown in FIG. 5B, tilt 512 is zero when thestylus is perpendicular/normal to the touch-sensitive surface (e.g.,when stylus 203 is parallel to normal 510) and the tilt increases as thestylus is tilted closer to being parallel to the touch-sensitivesurface.

Further, FIG. 5B illustrates distance 514 of stylus 203 relative to thetouch-sensitive surface. In some embodiments, distance 514 is thedistance from the tip of stylus 203 to the touch-sensitive surface, in adirection normal to the touch-sensitive surface. For example, in FIG.5B, distance 514 is the distance from the tip of stylus 203 to (x,y)position 504.

Although the terms, “x axis,” “y axis,” and “z axis,” are used herein toillustrate certain directions in particular figures, it will beunderstood that these terms do not refer to absolute directions. Inother words, an “x axis” could be any respective axis, and a “y axis”could be a particular axis that is distinct from the x axis. Typically,the x axis is perpendicular to the y axis. Similarly, a “z axis” isdistinct from the “x axis” and the “y axis,” and is typicallyperpendicular to both the “x axis” and the “y axis.”

Further, FIG. 5B illustrates roll 518, a rotation about the length (longaxis) of stylus 203.

Attention is now directed towards embodiments of user interfaces (“UI”)that are, optionally, implemented on portable multifunction device 100.

FIG. 6A illustrates an exemplary user interface for a menu ofapplications on portable multifunction device 100 in accordance withsome embodiments. Similar user interfaces are, optionally, implementedon device 300. In some embodiments, user interface 600 includes thefollowing elements, or a subset or superset thereof:

-   Signal strength indicator(s) 602 for wireless communication(s), such    as cellular and Wi-Fi signals;-   Time 604;-   Bluetooth indicator 605;-   Battery status indicator 606;-   Tray 608 with icons for frequently used applications, such as:    -   Icon 616 for telephone module 138, labeled “Phone,” which        optionally includes an indicator 614 of the number of missed        calls or voicemail messages;    -   Icon 618 for e-mail client module 140, labeled “Mail,” which        optionally includes an indicator 610 of the number of unread        e-mails;    -   Icon 620 for browser module 147, labeled “Browser;” and    -   Icon 622 for video and music player module 152, also referred to        as iPod (trademark of Apple Inc.) module 152, labeled “iPod;”        and-   Icons for other applications, such as:    -   Icon 624 for IM module 141, labeled “Messages;”    -   Icon 626 for calendar module 148, labeled “Calendar;”    -   Icon 628 for image management module 144, labeled “Photos;”    -   Icon 630 for camera module 143, labeled “Camera;”    -   Icon 632 for online video module 155, labeled “Online Video;”    -   Icon 634 for stocks widget 149-2, labeled “Stocks;”    -   Icon 636 for map module 154, labeled “Maps;”    -   Icon 638 for weather widget 149-1, labeled “Weather;”    -   Icon 640 for alarm clock widget 169-6, labeled “Clock;”    -   Icon 642 for workout support module 142, labeled “Workout        Support;”    -   Icon 644 for notes module 153, labeled “Notes;” and    -   Icon 646 for a settings application or module, which provides        access to settings for device 100 and its various applications        136.

It should be noted that the icon labels illustrated in FIG. 6A aremerely exemplary. For example, in some embodiments, icon 622 for videoand music player module 152 is labeled “Music” or “Music Player.” Otherlabels are, optionally, used for various application icons. In someembodiments, a label for a respective application icon includes a nameof an application corresponding to the respective application icon. Insome embodiments, a label for a particular application icon is distinctfrom a name of an application corresponding to the particularapplication icon.

FIG. 6B illustrates an exemplary user interface on a device (e.g.,device 300, FIG. 3) with a touch-sensitive surface 651 (e.g., a tabletor touchpad 355, FIG. 3) that is separate from display 650. Device 300also, optionally, includes one or more contact intensity sensors (e.g.,one or more of sensors 359) for detecting intensity of contacts ontouch-sensitive surface 651 and/or one or more tactile output generators359 for generating tactile outputs for a user of device 300.

FIG. 6B illustrates an exemplary user interface on a device (e.g.,device 300, FIG. 3) with a touch-sensitive surface 651 (e.g., a tabletor touchpad 355, FIG. 3) that is separate from display 650. Many of theexamples that follow will be given with reference to a device thatdetects inputs on a touch-sensitive surface that is separate from thedisplay, as shown in FIG. 6B. In some embodiments, the touch-sensitivesurface (e.g., 651 in FIG. 6B) has a primary axis (e.g., 652 in FIG. 6B)that corresponds to a primary axis (e.g., 653 in FIG. 6B) on the display(e.g., 650). In accordance with these embodiments, the device detectscontacts (e.g., 660 and 662 in FIG. 6B) with touch-sensitive surface 651at locations that correspond to respective locations on the display(e.g., in FIG. 6B, 660 corresponds to 668 and 662 corresponds to 670).In this way, user inputs (e.g., contacts 660 and 662, and movementsthereof) detected by the device on the touch-sensitive surface (e.g.,651 in FIG. 6B) are used by the device to manipulate the user interfaceon the display (e.g., 650 in FIG. 6B) of the multifunction device whenthe touch-sensitive surface is separate from the display. It should beunderstood that similar methods are, optionally, used for other userinterfaces described herein.

Additionally, while the following examples are given primarily withreference to finger inputs (e.g., finger contacts, finger tap gestures,finger swipe gestures, etc.), it should be understood that, in someembodiments, one or more of the finger inputs are replaced with inputfrom another input device (e.g., a stylus input).

As used herein, the term “focus selector” refers to an input elementthat indicates a current part of a user interface with which a user isinteracting. In some implementations that include a cursor or otherlocation marker, the cursor acts as a “focus selector,” so that when aninput (e.g., a press input) is detected on a touch-sensitive surface(e.g., touchpad 355 in FIG. 3 or touch-sensitive surface 651 in FIG. 6B)while the cursor is over a particular user interface element (e.g., abutton, window, slider or other user interface element), the particularuser interface element is adjusted in accordance with the detectedinput. In some implementations that include a touch-screen display(e.g., touch-sensitive display system 112 in FIG. 1A or the touch screenin FIG. 6A) that enables direct interaction with user interface elementson the touch-screen display, a detected contact on the touch-screen actsas a “focus selector,” so that when an input (e.g., a press input by thecontact) is detected on the touch-screen display at a location of aparticular user interface element (e.g., a button, window, slider orother user interface element), the particular user interface element isadjusted in accordance with the detected input. In some implementations,focus is moved from one region of a user interface to another region ofthe user interface without corresponding movement of a cursor ormovement of a contact on a touch-screen display (e.g., by using a tabkey or arrow keys to move focus from one button to another button); inthese implementations, the focus selector moves in accordance withmovement of focus between different regions of the user interface.Without regard to the specific form taken by the focus selector, thefocus selector is generally the user interface element (or contact on atouch-screen display) that is controlled by the user so as tocommunicate the user's intended interaction with the user interface(e.g., by indicating, to the device, the element of the user interfacewith which the user is intending to interact). For example, the locationof a focus selector (e.g., a cursor, a contact, or a selection box) overa respective button while a press input is detected on thetouch-sensitive surface (e.g., a touchpad or touch screen) will indicatethat the user is intending to activate the respective button (as opposedto other user interface elements shown on a display of the device).

As used in the specification and claims, the term “intensity” of acontact on a touch-sensitive surface refers to the force or pressure(force per unit area) of a contact (e.g., a finger contact or a styluscontact) on the touch-sensitive surface, or to a substitute (proxy) forthe force or pressure of a contact on the touch-sensitive surface. Theintensity of a contact has a range of values that includes at least fourdistinct values and more typically includes hundreds of distinct values(e.g., at least 256). Intensity of a contact is, optionally, determined(or measured) using various approaches and various sensors orcombinations of sensors. For example, one or more force sensorsunderneath or adjacent to the touch-sensitive surface are, optionally,used to measure force at various points on the touch-sensitive surface.In some implementations, force measurements from multiple force sensorsare combined (e.g., a weighted average or a sum) to determine anestimated force of a contact. Similarly, a pressure-sensitive tip of astylus is, optionally, used to determine a pressure of the stylus on thetouch-sensitive surface. Alternatively, the size of the contact areadetected on the touch-sensitive surface and/or changes thereto, thecapacitance of the touch-sensitive surface proximate to the contactand/or changes thereto, and/or the resistance of the touch-sensitivesurface proximate to the contact and/or changes thereto are, optionally,used as a substitute for the force or pressure of the contact on thetouch-sensitive surface. In some implementations, the substitutemeasurements for contact force or pressure are used directly todetermine whether an intensity threshold has been exceeded (e.g., theintensity threshold is described in units corresponding to thesubstitute measurements). In some implementations, the substitutemeasurements for contact force or pressure are converted to an estimatedforce or pressure and the estimated force or pressure is used todetermine whether an intensity threshold has been exceeded (e.g., theintensity threshold is a pressure threshold measured in units ofpressure). Using the intensity of a contact as an attribute of a userinput allows for user access to additional device functionality that mayotherwise not be readily accessible by the user on a reduced-size devicewith limited real estate for displaying affordances (e.g., on atouch-sensitive display) and/or receiving user input (e.g., via atouch-sensitive display, a touch-sensitive surface, or aphysical/mechanical control such as a knob or a button).

In some embodiments, contact/motion module 130 and/or 430 uses a set ofone or more intensity thresholds to determine whether an operation hasbeen performed by a user (e.g., to determine whether a user has“clicked” on an icon). In some embodiments, at least a subset of theintensity thresholds are determined in accordance with softwareparameters (e.g., the intensity thresholds are not determined by theactivation thresholds of particular physical actuators and can beadjusted without changing the physical hardware of device 100). Forexample, a mouse “click” threshold of a trackpad or touch-screen displaycan be set to any of a large range of predefined thresholds valueswithout changing the trackpad or touch-screen display hardware.Additionally, in some embodiments, a user of the device is provided withsoftware settings for adjusting one or more of the set of intensitythresholds (e.g., by adjusting individual intensity thresholds and/or byadjusting a plurality of intensity thresholds at once with asystem-level click “intensity” parameter).

As used in the specification and claims, the term “characteristicintensity” of a contact refers to a characteristic of the contact basedon one or more intensities of the contact. In some embodiments, thecharacteristic intensity is based on multiple intensity samples. Thecharacteristic intensity is, optionally, based on a predefined number ofintensity samples, or a set of intensity samples collected during apredetermined time period (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10seconds) relative to a predefined event (e.g., after detecting thecontact, prior to detecting liftoff of the contact, before or afterdetecting a start of movement of the contact, prior to detecting an endof the contact, before or after detecting an increase in intensity ofthe contact, and/or before or after detecting a decrease in intensity ofthe contact). A characteristic intensity of a contact is, optionallybased on one or more of: a maximum value of the intensities of thecontact, a mean value of the intensities of the contact, an averagevalue of the intensities of the contact, a top 10 percentile value ofthe intensities of the contact, a value at the half maximum of theintensities of the contact, a value at the 90 percent maximum of theintensities of the contact, or the like. In some embodiments, theduration of the contact is used in determining the characteristicintensity (e.g., when the characteristic intensity is an average of theintensity of the contact over time). In some embodiments, thecharacteristic intensity is compared to a set of one or more intensitythresholds to determine whether an operation has been performed by auser. For example, the set of one or more intensity thresholds mayinclude a low intensity threshold and a high intensity threshold. Inthis example, a contact with a characteristic intensity that does notexceed the low intensity threshold results in a first operation, acontact with a characteristic intensity that exceeds the low intensitythreshold and does not exceed the high intensity threshold results in asecond operation, and a contact with a characteristic intensity thatexceeds the high intensity threshold results in a third operation. Insome embodiments, a comparison between the characteristic intensity andone or more intensity thresholds is used to determine whether or not toperform one or more operations (e.g., whether to perform a respectiveoption or forgo performing the respective operation) rather than beingused to determine whether to perform a first operation or a secondoperation.

In some embodiments, a portion of a gesture is identified for purposesof determining a characteristic intensity. For example, atouch-sensitive surface may receive a continuous swipe contacttransitioning from a start location and reaching an end location (e.g.,a drag gesture), at which point the intensity of the contact increases.In this example, the characteristic intensity of the contact at the endlocation may be based on only a portion of the continuous swipe contact,and not the entire swipe contact (e.g., only the portion of the swipecontact at the end location). In some embodiments, a smoothing algorithmmay be applied to the intensities of the swipe contact prior todetermining the characteristic intensity of the contact. For example,the smoothing algorithm optionally includes one or more of: anunweighted sliding-average smoothing algorithm, a triangular smoothingalgorithm, a median filter smoothing algorithm, and/or an exponentialsmoothing algorithm. In some circumstances, these smoothing algorithmseliminate narrow spikes or dips in the intensities of the swipe contactfor purposes of determining a characteristic intensity.

The user interface figures (e.g., FIGS. 7A-7FF) described belowoptionally include various intensity diagrams that show the currentintensity of the contact on the touch-sensitive surface relative to oneor more intensity thresholds (e.g., a contact detection intensitythreshold IT₀, a light press intensity threshold I_(L), a deep pressintensity threshold I_(H), and/or one or more other intensitythresholds). This intensity diagram is typically not part of thedisplayed user interface, but is provided to aid in the interpretationof the figures. In some embodiments, the light press intensity thresholdcorresponds to an intensity at which the device will perform operationstypically associated with clicking a button of a physical mouse or atrackpad. In some embodiments, the deep press intensity thresholdcorresponds to an intensity at which the device will perform operationsthat are different from operations typically associated with clicking abutton of a physical mouse or a trackpad. In some embodiments, when acontact is detected with a characteristic intensity below the lightpress intensity threshold (e.g., and above a nominal contact-detectionintensity threshold IT₀ below which the contact is no longer detected),the device will move a focus selector in accordance with movement of thecontact on the touch-sensitive surface without performing an operationassociated with the light press intensity threshold or the deep pressintensity threshold. Generally, unless otherwise stated, these intensitythresholds are consistent between different sets of user interfacefigures.

In some embodiments, the response of the device to inputs detected bythe device depends on criteria based on the contact intensity during theinput. For example, for some “light press” inputs, the intensity of acontact exceeding a low intensity threshold during the input triggers afirst response. In some embodiments, the response of the device toinputs detected by the device depends on criteria that include both thecontact intensity during the input and time-based criteria. For example,for some “deep press” inputs, the intensity of a contact exceeding ahigh intensity threshold during the input, greater than the lowintensity threshold for a light press, triggers a second response onlyif a delay time has elapsed between meeting the low intensity thresholdand meeting the high intensity threshold. This delay time is typicallyless than 200 ms in duration (e.g., 40, 100, or 120 ms, depending on themagnitude of the high intensity threshold, with the delay timeincreasing as the high intensity threshold increases). This delay timehelps to avoid accidental deep press inputs. As another example, forsome “deep press” inputs, there is a reduced-sensitivity time periodthat occurs after the time at which the low intensity threshold is met.During the reduced-sensitivity time period, the high intensity thresholdis increased. This temporary increase in the high intensity thresholdalso helps to avoid accidental deep press inputs. For other deep pressinputs, the response to detection of a deep press input does not dependon time-based criteria.

In some embodiments, one or more of the input intensity thresholdsand/or the corresponding outputs vary based on one or more factors, suchas user settings, contact motion, input timing, application running,rate at which the intensity is applied, number of concurrent inputs,user history, environmental factors (e.g., ambient noise), focusselector position, and the like. Exemplary factors are described in U.S.patent application Ser. Nos. 14/399,606 and 14/624,296, which areincorporated by reference herein in their entireties.

For example, FIG. 6C illustrates a dynamic intensity threshold 680 thatchanges over time based in part on the intensity of touch input 676 overtime. Dynamic intensity threshold 680 is a sum of two components, firstcomponent 674 that decays over time after a predefined delay time p1from when touch input 676 is initially detected, and second component678 that trails the intensity of touch input 676 over time. The initialhigh intensity threshold of first component 674 reduces accidentaltriggering of a “deep press” response, while still allowing an immediate“deep press” response if touch input 676 provides sufficient intensity.Second component 678 reduces unintentional triggering of a “deep press”response by gradual intensity fluctuations of a touch input. In someembodiments, when touch input 676 satisfies dynamic intensity threshold680 (e.g., at point 681 in FIG. 6C), the “deep press” response istriggered.

FIG. 6D illustrates another dynamic intensity threshold 686 (e.g.,intensity threshold I_(D)). FIG. 6D also illustrates two other intensitythresholds: a first intensity threshold I_(H) and a second intensitythreshold I_(L). In FIG. 6D, although touch input 684 satisfies thefirst intensity threshold I_(H) and the second intensity threshold I_(L)prior to time p2, no response is provided until delay time p2 haselapsed at time 682. Also in FIG. 6D, dynamic intensity threshold 686decays over time, with the decay starting at time 688 after a predefineddelay time p1 has elapsed from time 682 (when the response associatedwith the second intensity threshold I_(L) was triggered). This type ofdynamic intensity threshold reduces accidental triggering of a responseassociated with the dynamic intensity threshold I_(D) immediately after,or concurrently with, triggering a response associated with a lowerintensity threshold, such as the first intensity threshold I_(H) or thesecond intensity threshold I_(L).

FIG. 6E illustrate yet another dynamic intensity threshold 692 (e.g.,intensity threshold I_(D)). In FIG. 6E, a response associated with theintensity threshold I_(L) is triggered after the delay time p2 haselapsed from when touch input 690 is initially detected. Concurrently,dynamic intensity threshold 692 decays after the predefined delay timep1 has elapsed from when touch input 690 is initially detected. So adecrease in intensity of touch input 690 after triggering the responseassociated with the intensity threshold I_(L), followed by an increasein the intensity of touch input 690, without releasing touch input 690,can trigger a response associated with the intensity threshold I_(D)(e.g., at time 694) even when the intensity of touch input 690 is belowanother intensity threshold, for example, the intensity threshold I_(L).

An increase of characteristic intensity of the contact from an intensitybelow the light press intensity threshold I_(L) to an intensity betweenthe light press intensity threshold I_(L) and the deep press intensitythreshold I_(H) is sometimes referred to as a “light press” input. Anincrease of characteristic intensity of the contact from an intensitybelow the deep press intensity threshold I_(H) to an intensity above thedeep press intensity threshold I_(H) is sometimes referred to as a “deeppress” input. An increase of characteristic intensity of the contactfrom an intensity below the contact-detection intensity threshold IT₀ toan intensity between the contact-detection intensity threshold IT₀ andthe light press intensity threshold I_(L) is sometimes referred to asdetecting the contact on the touch-surface. A decrease of characteristicintensity of the contact from an intensity above the contact-detectionintensity threshold IT₀ to an intensity below the contact-detectionintensity threshold IT₀ is sometimes referred to as detecting liftoff ofthe contact from the touch-surface. In some embodiments IT₀ is zero. Insome embodiments, IT₀ is greater than zero. In some illustrations ashaded circle or oval is used to represent intensity of a contact on thetouch-sensitive surface. In some illustrations, a circle or oval withoutshading is used represent a respective contact on the touch-sensitivesurface without specifying the intensity of the respective contact.

In some embodiments, described herein, one or more operations areperformed in response to detecting a gesture that includes a respectivepress input or in response to detecting the respective press inputperformed with a respective contact (or a plurality of contacts), wherethe respective press input is detected based at least in part ondetecting an increase in intensity of the contact (or plurality ofcontacts) above a press-input intensity threshold. In some embodiments,the respective operation is performed in response to detecting theincrease in intensity of the respective contact above the press-inputintensity threshold (e.g., the respective operation is performed on a“down stroke” of the respective press input). In some embodiments, thepress input includes an increase in intensity of the respective contactabove the press-input intensity threshold and a subsequent decrease inintensity of the contact below the press-input intensity threshold, andthe respective operation is performed in response to detecting thesubsequent decrease in intensity of the respective contact below thepress-input threshold (e.g., the respective operation is performed on an“up stroke” of the respective press input).

In some embodiments, the device employs intensity hysteresis to avoidaccidental inputs sometimes termed “jitter,” where the device defines orselects a hysteresis intensity threshold with a predefined relationshipto the press-input intensity threshold (e.g., the hysteresis intensitythreshold is X intensity units lower than the press-input intensitythreshold or the hysteresis intensity threshold is 75%, 90%, or somereasonable proportion of the press-input intensity threshold). Thus, insome embodiments, the press input includes an increase in intensity ofthe respective contact above the press-input intensity threshold and asubsequent decrease in intensity of the contact below the hysteresisintensity threshold that corresponds to the press-input intensitythreshold, and the respective operation is performed in response todetecting the subsequent decrease in intensity of the respective contactbelow the hysteresis intensity threshold (e.g., the respective operationis performed on an “up stroke” of the respective press input).Similarly, in some embodiments, the press input is detected only whenthe device detects an increase in intensity of the contact from anintensity at or below the hysteresis intensity threshold to an intensityat or above the press-input intensity threshold and, optionally, asubsequent decrease in intensity of the contact to an intensity at orbelow the hysteresis intensity, and the respective operation isperformed in response to detecting the press input (e.g., the increasein intensity of the contact or the decrease in intensity of the contact,depending on the circumstances).

For ease of explanation, the description of operations performed inresponse to a press input associated with a press-input intensitythreshold or in response to a gesture including the press input are,optionally, triggered in response to detecting: an increase in intensityof a contact above the press-input intensity threshold, an increase inintensity of a contact from an intensity below the hysteresis intensitythreshold to an intensity above the press-input intensity threshold, adecrease in intensity of the contact below the press-input intensitythreshold, or a decrease in intensity of the contact below thehysteresis intensity threshold corresponding to the press-inputintensity threshold. Additionally, in examples where an operation isdescribed as being performed in response to detecting a decrease inintensity of a contact below the press-input intensity threshold, theoperation is, optionally, performed in response to detecting a decreasein intensity of the contact below a hysteresis intensity thresholdcorresponding to, and lower than, the press-input intensity threshold.As described above, in some embodiments, the triggering of theseresponses also depends on time-based criteria being met (e.g., a delaytime has elapsed between a low intensity threshold being met and a highintensity threshold being met).

User Interfaces and Associated Processes

Attention is now directed towards embodiments of user interfaces (“UI”)and associated processes that may be implemented on an electronicdevice, such as portable multifunction device 100 or device 300, with adisplay, a touch-sensitive surface, and one or more sensors to detectintensity of contacts with the touch-sensitive surface.

FIGS. 7A-7FF illustrate exemplary user interfaces for processing touchinputs with instructions in a web page in accordance with someembodiments. The user interfaces in these figures are used to illustratethe processes described below, including the processes in FIGS. 8A-8Cand FIG. 9. Although some of the examples which follow will be givenwith reference to inputs on a touch-sensitive surface 651 that isseparate from display 650, in some embodiments, the device detectsinputs on a touch-screen display (where the touch-sensitive surface andthe display are combined), as shown in FIG. 6A.

FIG. 7A illustrates that a user interface 702 on display 650 includes auser interface of a web browser application (e.g., browser module 147,FIG. 3). The user interface of the web browser application includesdisplay of a portion of a web page (e.g., web page 185, FIG. 3) thatincludes an image 704. FIG. 7A also illustrates that touch input 707(e.g., a finger or stylus contact) is detected on touch-sensitivesurface 651 at a location that corresponds to the displayed portion ofthe web page (e.g., focus selector 706, such as a cursor, is on thedisplayed portion of the web page). In FIG. 7A, intensity diagram 730indicates that an intensity applied by touch input 707 ontouch-sensitive surface 651 is increasing over time.

In FIG. 7B, intensity diagram 730 indicates that the intensity appliedby touch input 707 on touch-sensitive surface 651 continues to increaseover time and reaches a low intensity threshold I_(L) (or the intensityapplied by touch input 707 has changed from below the low intensitythreshold I_(L) to above the low intensity threshold I_(L)).

Intensity diagram 730 in FIG. 7B illustrates that the device generatesmouse down event 740 in response to the intensity applied by touch input707 on touch-sensitive surface 651 reaching the low intensity thresholdI_(L) (or the intensity applied by touch input 707 changing from belowthe low intensity threshold I_(L) to above the low intensity thresholdI_(L)). In some embodiments, a mouse down event indicates that an inputbutton (e.g., a mouse button or trackpad button) has been pressed orthat another input (e.g., a touch input pressing touch-sensitive surface651 with a sufficient intensity) that meets predefined criteria forgenerating or triggering a mouse down event has been received. Thus, insome embodiments, the device generates a mouse down event in response todetermining that an input button, of a mouse or a similar input device(e.g., a trackpad) in communication with the device, has been pressed,independent of an intensity detected on touch-sensitive surface 651. Insome embodiments, when the web browser or the web page includesinstructions for handling the mouse down event, the device processes themouse down event in accordance with the instructions for handling themouse down event in the web browser or the web page (e.g., pressing amouse button while focus selector 706 is displayed over a scrollbarinitiates scrolling a displayed portion of the web page).

Intensity diagram 730 in FIG. 7B also illustrates that, optionally,“will begin” event 742 (also called herein a “force will begin” event)is generated in response to the intensity applied by touch input 707 ontouch-sensitive surface 651 reaching the low intensity threshold I_(L)(or the intensity applied by touch input 707 has changed from below thelow intensity threshold I_(L) to above the low intensity thresholdI_(L)). In some embodiments, a will begin event is used to indicate thatone or more force events are expected (e.g., because an intensitythreshold for generating a force event has been satisfied or adifference between a current intensity and the intensity threshold forgenerating a force event is small).

FIG. 7B also illustrates that, in response to the intensity applied bytouch input 707 on touch-sensitive surface 651 reaching the lowintensity threshold I_(L) (or the intensity applied by touch input 707changing from below the low intensity threshold I_(L) to above the lowintensity threshold I_(L)), the device generates a tactile output of afirst type (e.g., using tactile output generator(s) 357 in FIG. 3). Atactile output of the first type provides feedback to the userindicating that the intensity of the contact has increased to (or risenabove) the low intensity threshold I_(L). In the example illustrated inFIG. 7B, a mouse down event is generated in temporal proximity to (e.g.,immediately before, during, or immediately after) generation of thetactile output of the first type. As such, the tactile output in FIG. 7Bprovides feedback to the user that a mouse down event associated withthe change in intensity of the contact has been (or will be) generated.

In FIG. 7C, intensity diagram 730 illustrates that the intensity appliedby touch input 707 on touch-sensitive surface 651 continues to increaseover time, and, in response to a change (e.g., an increase) to theintensity applied by touch input 707 on touch-sensitive surface 651, thedevice generates force changed event 744.

FIG. 7D illustrates, in intensity diagram 730, that the intensityapplied by touch input 707 on touch-sensitive surface 651 has increasedto reach a high intensity threshold I_(H) (or the intensity applied bytouch input 707 has changed from below the high intensity thresholdI_(H) to above the high intensity threshold I_(H)), and, in response tothe intensity applied by touch input 707 on touch-sensitive surface 651reaching the high intensity threshold I_(H) (or the intensity applied bytouch input 707 changing from below the high intensity threshold I_(H)to above the high intensity threshold I_(H)), the device generates forcedown event 746. Force down event 746 indicates that the intensityapplied by touch input 707 on touch-sensitive surface 651 has reachedthe high intensity threshold I_(H) (or the intensity applied by touchinput 707 has changed from below the high intensity threshold I_(H) toabove the high intensity threshold I_(H)).

FIG. 7D also illustrates that, in response to the intensity applied bytouch input 707 on touch-sensitive surface 651 reaching the highintensity threshold I_(H) (or the intensity applied by touch input 707changing from below the high intensity threshold I_(H) to above the highintensity threshold I_(H)), user interface 702 is updated to displayregion 708. In some embodiments, region 708 includes an enlarged image(e.g., an enlargement of image 704). In some embodiments, region 708includes a video (e.g., a screenshot of the video is shown in region708, and an activation of the screenshot, such as a click on thescreenshot, initiates a playback of the video).

In some embodiments, when the web browser or the web page includesinstructions for handling the force down event, the device processes theforce down event in accordance with the instructions for handling theforce down event in the web browser or the web page (e.g., displayingregion 708 in accordance with instructions for handling the force downevent in the web page).

FIG. 7D illustrates that, in response to the intensity applied by touchinput 707 on touch-sensitive surface 651 reaching the high intensitythreshold I_(H) (or the intensity applied by touch input 707 changingfrom below the high intensity threshold I_(H) to above the highintensity threshold I_(H)), the device generates a tactile output of asecond type (e.g., using tactile output generator(s) 357 in FIG. 3). Atactile output of the second type provides feedback to the userindicating that the intensity of the contact has increased to (or risenabove) the high intensity threshold I_(H). In the example illustrated inFIG. 7D, a force down event is generated in temporal proximity to (e.g.,immediately before, during, or immediately after) generation of thetactile output of the second type. As such, the tactile output in FIG.7D provides feedback to the user that a force down event associated withthe change in intensity of the contact has been (or will be) generated.In some embodiments, a tactile output of a second type is distinct froma tactile output of a first type.

In FIG. 7E, intensity diagram 730 illustrates that the intensity appliedby touch input 707 on touch-sensitive surface 651 continues to increaseover time, and, in response to a change (e.g., an increase) to theintensity applied by touch input 707 on touch-sensitive surface 651, thedevice generates force changed event 748.

Intensity diagram 730 in FIG. 7F illustrates that the intensity appliedby touch input 707 on touch-sensitive surface 651 is maintained (e.g.,the intensity has not changed) for a period of time, and the device doesnot generate a force changed event while the intensity applied by touchinput 707 does not change. In addition, touch input 707 ontouch-sensitive surface 651 has not moved across touch-sensitive surface651, and the device does not generate a mouse moved event while touchinput 707 does not move across touch-sensitive surface 651.

FIG. 7G illustrates, in intensity diagram 730, that the intensityapplied by touch input 707 on touch-sensitive surface 651 decreases tothe high intensity threshold I_(H) (or the intensity applied by touchinput 707 has changed from above the high intensity threshold I_(H) tobelow the high intensity threshold I_(H)), and, in response to theintensity applied by touch input 707 on touch-sensitive surface 651decreasing to the high intensity threshold I_(H) (or the intensityapplied by touch input 707 changing from above the high intensitythreshold I_(H) to below the high intensity threshold I_(H)), the devicegenerates force up event 750. Force up event 750 indicates that theintensity applied by touch input 707 on touch-sensitive surface 651 hasfallen to the high intensity threshold I_(H) (or the intensity appliedby touch input 707 has changed from above the high intensity thresholdI_(H) to below the high intensity threshold I_(H)).

FIG. 7G also illustrates that, in response to the intensity applied bytouch input 707 on touch-sensitive surface 651 decreasing to the highintensity threshold I_(H) (or the intensity applied by touch input 707changing from above the high intensity threshold I_(H) to below the highintensity threshold I_(H)), region 708 (e.g., for playing a video ordisplaying an enlarged image as illustrated in FIG. 7F) is visuallydistinguished (e.g., color, line width, highlighting, and/or linepattern are changed). For example, a border of region 708 is visuallydistinguished, such as highlighted, to indicate that region 708 is“locked.” When the region 708 is locked, region 708 remains on display650 subsequent to the intensity applied by touch input 707 ontouch-sensitive surface 651 decreasing to the high intensity thresholdI_(H) (or the intensity applied by touch input 707 changing from abovethe high intensity threshold I_(H) to below the high intensity thresholdI_(H)). Alternatively, in some embodiments, in response to the intensityapplied by touch input 707 on touch-sensitive surface 651 decreasing tothe high intensity threshold I_(H) (or the intensity applied by touchinput 707 changing from above the high intensity threshold I_(H) tobelow the high intensity threshold I_(H)), region 708 (e.g., for playinga video or displaying an enlarged image as illustrated in FIG. 7F)ceases to be displayed in user interface 702.

In some embodiments, when the web browser or the web page includesinstructions for handling the force up event, the device processes theforce up event in accordance with the instructions for handling theforce up event in the web browser or the web page (e.g., visuallydistinguishing display region 708 in accordance with instructions in theweb page for handling the force up event, or alternatively, ceasing todisplay region 708 in accordance with instructions in the web page forhandling the force up event).

FIG. 7G illustrates that, in response to the intensity applied by touchinput 707 on touch-sensitive surface 651 decreasing to the highintensity threshold I_(H) (or the intensity applied by touch input 707changing from above the high intensity threshold I_(H) to below the highintensity threshold I_(H)), the device generates a tactile output of athird type (e.g., using tactile output generator(s) 357 in FIG. 3). Atactile output of the third type provides feedback to the userindicating that the intensity of the contact has decreased to (or hasfallen below) the high intensity threshold I_(H). In the exampleillustrated in FIG. 7G, a force up event is generated in temporalproximity to (e.g., immediately before, during, or immediately after)generation of the tactile output of the third type. As such, the tactileoutput in FIG. 7G provides feedback to the user that a force up eventassociated with the change in intensity of the contact has been (or willbe) generated. In some embodiments, a tactile output of a third type isdistinct from a tactile output of a first type and a tactile output of asecond type.

In FIG. 7H, intensity diagram 730 illustrates that the intensity appliedby touch input 707 on touch-sensitive surface 651 continues to decreaseover time, and, in response to a change (e.g., a decrease) to theintensity applied by touch input 707 on touch-sensitive surface 651, thedevice generates force changed event 752.

FIG. 7I illustrates, in intensity diagram 730, that the intensityapplied by touch input 707 on touch-sensitive surface 651 continues todecrease to the low intensity threshold I_(L) (or the intensity appliedby touch input 707 has changed from above the low intensity thresholdI_(L) to below the low intensity threshold I_(L)), and, in response tothe intensity applied by touch input 707 on touch-sensitive surface 651decreasing to the low intensity threshold I_(L) (or the intensityapplied by touch input 707 changing from above the low intensitythreshold I_(L) to below the low intensity threshold I_(L)), the devicegenerates mouse up event 754. In some embodiments, a mouse up eventindicates that an input button (e.g., a mouse button) has been releasedor that another input (e.g., a touch input) that meets predefined mouseup criteria has been received. Thus, in some embodiments, the devicegenerates a mouse up event in response to determining that an inputbutton, of a mouse or a similar input device (e.g., a trackpad) incommunication with the device, has been released, independent of anintensity detected on touch-sensitive surface 651. In some embodiments,when the web browser or the web page includes instructions for handlingthe mouse up event, the device processes the mouse up event inaccordance with the instructions for handling the mouse up event in theweb browser or the web page (e.g., releasing a mouse button, afterpressing the mouse button, while focus selector 706 is displayed overthe displayed representation of a hyperlink, initiates displaying a webpage that is indicated by the hyperlink). In FIG. 7I, in response to theintensity applied by touch input 707 on touch-sensitive surface 651decreasing to the low intensity threshold I_(L) (or the intensityapplied by touch input 707 changing from above the low intensitythreshold I_(L) to below the low intensity threshold I_(L)), region 708(e.g., as illustrated in FIG. 7F) ceases to be displayed in userinterface 702. Alternatively, subsequent to the intensity applied bytouch input 707 on touch-sensitive surface 651 reaching the highintensity threshold I_(H) (or the intensity applied by touch input 707changing from below the high intensity threshold I_(H) to above the highintensity threshold I_(H)), region 708 remains on user interface 702independent of subsequent intensity applied by touch input 707 ontouch-sensitive surface 651 (e.g., region 708 remains in user interface702 even after touch input 707 ceases to be detected on touch-sensitivesurface 651).

FIG. 7I also illustrates that, in response to the intensity applied bytouch input 707 on touch-sensitive surface 651 decreasing to the lowintensity threshold I_(L) (or the intensity applied by touch input 707changing from above the low intensity threshold I_(L) to below the lowintensity threshold I_(L)), the device generates a tactile output of afourth type (e.g., using tactile output generator(s) 357 in FIG. 3). Atactile output of the fourth type provides feedback to the userindicating that the intensity of the contact has decreased to (or fallenbelow) the low intensity threshold I_(L). In the example illustrated inFIG. 7I, a mouse up event is generated in temporal proximity to (e.g.,immediately before, during, or immediately after) generation of thetactile output of the fourth type. As such, the tactile output in FIG.7I provides feedback to the user that a mouse up event associated withthe change in intensity of the contact has been (or will be) generated.In some embodiments, a tactile output of a fourth type is distinct froma tactile output of a first type, a tactile output of a second type, anda tactile output of a third type.

Intensity diagram 730 in FIG. 7J illustrates that the intensity appliedby touch input 707 on touch-sensitive surface 651 continues to decrease.In some embodiments, a force changed event is not generated (e.g.,generating a force changed event is forgone) in accordance with adetermination that the intensity applied by touch input 707 ontouch-sensitive surface 651 is below the low intensity threshold I_(L).

FIGS. 7K-7L illustrates that, in some embodiments, a force up event isgenerated in response to the intensity applied by touch input 707 ontouch-sensitive surface 651 decreasing to a force down intensitythreshold I_(HD) that is distinct from the high intensity thresholdI_(H), instead of the intensity applied by touch input 707 ontouch-sensitive surface 651 decreasing to the high intensity thresholdI_(H) (or the intensity applied by touch input 707 changing from abovethe force down intensity threshold I_(HD) to below the force downintensity threshold I_(HD)).

Intensity diagram 730 in FIG. 7K illustrates that the intensity appliedby touch input 707 on touch-sensitive surface 651 decreases to the highintensity threshold I_(H) (or the intensity applied by touch input 707has changed from above the high intensity threshold I_(H) to below thehigh intensity threshold I_(H)), and, in response to the intensityapplied by touch input 707 on touch-sensitive surface 651 decreasing tothe high intensity threshold I_(H) (or the intensity applied by touchinput 707 changing from above the high intensity threshold I_(H) tobelow the high intensity threshold I_(H)), the device generates forcechanged event 756 (e.g., because the intensity has changed) instead ofgenerating a force up event.

FIG. 7L illustrates that the intensity applied by touch input 707 ontouch-sensitive surface 651 decreases to the force up intensitythreshold I_(HD) (or the intensity applied by touch input 707 haschanged from above the force up intensity threshold I_(HD) to below theforce up intensity threshold I_(HD)), and, in response to the intensityapplied by touch input 707 on touch-sensitive surface 651 decreasing tothe force up intensity threshold I_(HD) (or the intensity applied bytouch input 707 changing from above the force up intensity thresholdI_(HD) to below the force up intensity threshold I_(HD)), the devicegenerates force up event 758.

FIG. 7L also illustrates that, in response to the intensity applied bytouch input 707 on touch-sensitive surface 651 decreasing to the forceup intensity threshold I_(HD) (or the intensity applied by touch input707 changing from above the force up intensity threshold I_(HD) to belowthe force up intensity threshold I_(HD)), the device generates a tactileoutput of a third type (e.g., using tactile output generator(s) 357 inFIG. 3). A tactile output of the third type provides feedback to theuser indicating that the intensity of the contact has decreased to (orbelow) the force up intensity threshold I_(HD). In the exampleillustrated in FIG. 7L, a force up event is generated in temporalproximity to (e.g., immediately before, during, or immediately after)generation of the tactile output of the third type. As such, the tactileoutput in FIG. 7L provides feedback to the user that a force up eventassociated with the change in intensity of the contact has been (or willbe) generated.

FIG. 7M illustrates that the intensity applied by touch input 707 ontouch-sensitive surface 651 decreases to a mouse up intensity thresholdI_(LD) (or the intensity applied by touch input 707 has changed fromabove the mouse up intensity threshold I_(LD) to below the mouse upintensity threshold I_(LD)), and, in response to the intensity appliedby touch input 707 on touch-sensitive surface 651 decreasing to themouse up intensity threshold I_(LD) (or the intensity applied by touchinput 707 changing from above the mouse up intensity threshold I_(LD) tobelow the mouse up intensity threshold I_(LD)), the device generatesmouse up event 760.

FIG. 7M also illustrates that, in response to the intensity applied bytouch input 707 on touch-sensitive surface 651 decreasing to the mouseup intensity threshold I_(LD) (or the intensity applied by touch input707 changing from above the mouse up intensity threshold I_(LD) to belowthe mouse up intensity threshold I_(LD)), the device generates a tactileoutput of a fourth type (e.g., using tactile output generator(s) 357 inFIG. 3). A tactile output of the fourth type provides feedback to theuser indicating that the intensity of the contact has decreased to (orbelow) the mouse up intensity threshold I_(LD). In the exampleillustrated in FIG. 7M, a mouse up event is generated in temporalproximity to (e.g., immediately before, during, or immediately after)generation of the tactile output of the fourth type. As such, thetactile output in FIG. 7M provides feedback to the user that a mouse upevent associated with the change in intensity of the contact has been(or will be) generated.

FIG. 7N illustrates that touch input 709 on touch-sensitive surface 651moves across touch-sensitive surface 651 and focus selector 706 movesacross display 650 in accordance with a movement of touch input 709across touch-sensitive surface 651. Intensity diagram 730 in FIG. 7Nillustrates that multiple mouse moved events 762 are generated inresponse to touch input 709 on touch-sensitive surface 651 moving acrosstouch-sensitive surface 651.

FIGS. 7O-7S illustrate operations associated with touch input 711 inaccordance with some embodiments.

FIG. 7O illustrates that focus selector 706 has moved to a location ondisplay 650 that corresponds to the word “Gettysburg” in the web page.FIG. 7O also illustrates that touch input 711 is detected ontouch-sensitive surface 651 and the intensity applied by touch input 711on touch-sensitive surface 651 increases over time.

In FIG. 7P, intensity diagram 730 illustrates that the intensity appliedby touch input 711 on touch-sensitive surface 651 continues to increaseover time and reaches the low intensity threshold I_(L) (or theintensity applied by touch input 711 has changed from below the lowintensity threshold I_(L) to above the low intensity threshold I_(L)).Intensity diagram 730 in FIG. 7P also illustrates that the devicegenerates mouse down event 764 and optionally, a will begin event 766.

FIG. 7P also illustrates that, in response to the intensity applied bytouch input 711 on touch-sensitive surface 651 reaching the lowintensity threshold I_(L) (or the intensity applied by touch input 711changing from below the low intensity threshold I_(L) to above the lowintensity threshold I_(L)), the device generates a tactile output of thefirst type (e.g., using tactile output generator(s) 357 in FIG. 3). Atactile output of the first type provides feedback to the userindicating that the intensity of the contact has increased to (or risenabove) the low intensity threshold I_(L). In the example illustrated inFIG. 7P, a mouse down event is generated in temporal proximity to (e.g.,immediately before, during, or immediately after) generation of thetactile output of the first type. As such, the tactile output in FIG. 7Pprovides feedback to the user that a mouse down event associated withthe change in intensity of the contact has been (or will be) generated.

Intensity diagram 730 in FIG. 7Q illustrates that the intensity appliedby touch input 711 on touch-sensitive surface 651 continues to increaseover time, and, in response to a change (e.g., an increase) to theintensity applied by touch input 711 on touch-sensitive surface 651, thedevice generates force changed event 768. FIG. 7Q also illustrates thatpopup view 710 is displayed in response to the intensity applied bytouch input 711 on touch-sensitive surface 651 increasing above the lowintensity threshold I_(L).

FIG. 7R illustrates, in intensity diagram 730, that the intensityapplied by touch input 711 on touch-sensitive surface 651 has increasedto reach the high intensity threshold I_(H) (or the intensity applied bytouch input 711 has changed from below the high intensity thresholdI_(H) to above the high intensity threshold I_(H)), and, in response tothe intensity applied by touch input 711 on touch-sensitive surface 651reaching the high intensity threshold I_(H) (or the intensity applied bytouch input 711 changing from below the high intensity threshold I_(H)to above the high intensity threshold I_(H)), the device generates forcedown event 770.

FIG. 7R also illustrates that, in response to the intensity applied bytouch input 711 on touch-sensitive surface 651 reaching the highintensity threshold I_(H) (or the intensity applied by touch input 711changing from below the high intensity threshold I_(H) to above the highintensity threshold I_(H)), the device generates a tactile output of thesecond type (e.g., using tactile output generator(s) 357 in FIG. 3). Atactile output of the second type provides feedback to the userindicating that the intensity of the contact has increased to (or risenabove) the high intensity threshold I_(H). In the example illustrated inFIG. 7R, a force down event is generated in temporal proximity to (e.g.,immediately before, during, or immediately after) generation of thetactile output of the second type. As such, the tactile output in FIG.7R provides feedback to the user that a force down event associated withthe change in intensity of the contact has been (or will be) generated.

In some embodiments, a size of popup view 710 increases with theintensity applied by touch input 711 on touch-sensitive surface 651until the intensity reaches the high intensity threshold I_(H). In someembodiments, in response to the intensity applied by touch input 711 ontouch-sensitive surface 651 reaching the high intensity threshold I_(H)(or the intensity applied by touch input 711 changing from below thehigh intensity threshold I_(H) to above the high intensity thresholdI_(H)), popup view 710 is “locked” on display 650. For example, afterthe intensity applied by touch input 711 on touch-sensitive surface 651reaching the high intensity threshold I_(H), popup view 710 remains ondisplay 650 at the same size independent of a subsequent decrease of theintensity applied by touch input 711 on touch-sensitive surface 651below the high intensity threshold I_(H).

In FIGS. 7Q-7R, popup view 710 includes a dictionary lookup of acorresponding word or phrase (e.g., “Gettysburg”). In some embodiments,popup view 710 is “locked” in accordance with instructions, in the webbrowser, for handling a force down event.

In FIG. 7S, intensity diagram 730 illustrates that the intensity appliedby touch input 711 on touch-sensitive surface 651 continues to increaseover time, and, in response to a change (e.g., an increase) to theintensity applied by touch input 711 on touch-sensitive surface 651, thedevice generates force changed event 772. In some embodiments, becausepopup view 710 is locked when the intensity applied by touch input 711on touch-sensitive surface 651 reaches the high intensity thresholdI_(H), the size of the popup view 710 does not increase further with thesubsequent increase in the intensity applied by touch input 711, asshown in FIG. 7S. This is an example of an application receiving a forcechanged event, but making no change to the user interface correspondingto the application, or at least not change that correspond to the changein intensity of the touch input. More generally stated, in somecircumstances, an application receiving a force changed event makes nocorresponding change to the user interface corresponding to thatapplication. On the other hand, optionally, an internal state of theapplication is updated in response to the force changed event, forexample, by updating an internal state value that indicates a lastreported intensity of the touch input, as reported by the last receivedforce changed event.

FIGS. 7T-7V illustrate operations associated with touch input 711 inaccordance with some other embodiments.

In FIG. 7T, intensity diagram 730 illustrates that the intensity appliedby touch input 711 on touch-sensitive surface 651 reaches the lowintensity threshold I_(L) (or the intensity applied by touch input 711has changed from below the low intensity threshold I_(L) to above thelow intensity threshold I_(L)). Intensity diagram 730 in FIG. 7T alsoillustrates that the device generates mouse down event 774 andoptionally, will begin event 776, in response to the intensity appliedby touch input 711 on touch-sensitive surface 651 reaching the lowintensity threshold I_(L) (or the intensity applied by touch input 711changing from below the low intensity threshold I_(L) to above the lowintensity threshold I_(L)).

FIG. 7T also illustrates that, in response to the intensity applied bytouch input 711 on touch-sensitive surface 651 reaching the lowintensity threshold I_(L) (or the intensity applied by touch input 711changing from below the low intensity threshold I_(L) to above the lowintensity threshold I_(L)), the device generates a tactile output of thefirst type (e.g., using tactile output generator(s) 357 in FIG. 3). Atactile output of the first type provides feedback to the userindicating that the intensity of the contact has increased to (or risenabove) the low intensity threshold I_(L). In the example illustrated inFIG. 7T, a mouse down event is generated in temporal proximity to (e.g.,immediately before, during, or immediately after) generation of thetactile output of the first type. As such, the tactile output in FIG. 7Tprovides feedback to the user that a mouse down event associated withthe change in intensity of the contact has been (or will be) generated.

Intensity diagram 730 in FIG. 7U illustrates that the intensity appliedby touch input 711 on touch-sensitive surface 651 continues to increaseover time, and, in response to a change (e.g., an increase) to theintensity applied by touch input 711 on touch-sensitive surface 651, thedevice generates force changed event 778. FIG. 7U also illustrates thatpopup view 712, instead of popup view 710 (FIG. 7Q) is displayed inresponse to the intensity applied by touch input 711 on touch-sensitivesurface 651 increasing above the low intensity threshold I_(L).

FIG. 7V illustrates, in intensity diagram 730, that the intensityapplied by touch input 711 on touch-sensitive surface 651 has increasedto reach the high intensity threshold I_(H) (or the intensity applied bytouch input 711 has changed from below the high intensity thresholdI_(H) to above the high intensity threshold I_(H)), and, in response tothe intensity applied by touch input 711 on touch-sensitive surface 651reaching the high intensity threshold I_(H) (or the intensity applied bytouch input 711 changing from below the high intensity threshold I_(H)to above the high intensity threshold I_(H)), the device generates forcedown event 780.

FIG. 7V also illustrates that, in response to the intensity applied bytouch input 711 on touch-sensitive surface 651 reaching the highintensity threshold I_(H) (or the intensity applied by touch input 711changing from below the high intensity threshold I_(H) to above the highintensity threshold I_(H)), the device generates a tactile output of thesecond type (e.g., using tactile output generator(s) 357 in FIG. 3). Atactile output of the second type provides feedback to the userindicating that the intensity of the contact has increased to (or risenabove) the high intensity threshold I_(H). In the example illustrated inFIG. 7V, a force down event is generated in temporal proximity to (e.g.,immediately before, during, or immediately after) generation of thetactile output of the second type. As such, the tactile output in FIG.7V provides feedback to the user that a force down event associated withthe change in intensity of the contact has been (or will be) generated.

In FIGS. 7U-7V, popup view 712 includes a map of a location thatcorresponds to the selected word or phrase (e.g., “Gettysburg”). In someembodiments, popup view 712 is configured in accordance withinstructions in the web page (e.g., instructions, in the web page, forprocessing a force changed event to change a size of popup view 712 andinstructions, in the web page, for processing a force down event to lockthe size of popup view 712).

In some embodiments, both the web browser and the web page includeinstructions for processing a force event of a same type (e.g., a forcechanged event, a force down event, or a force up event). In someembodiments, the device forgoes processing a force event in accordancewith instructions in the web browser for processing the force event andprocesses the force event in accordance with instructions in the webpage for processing the force event. More specifically, in someembodiments, the device disables execution of a set of instructionsincluded in the web browser (e.g., the aforementioned instructions forprocessing one or more particular types of force event) in response tothe will begin event. For example, in response to the will begin event,instructions in the web page that disable default processing of the oneor more particular types of force events are executed. In someembodiments, disabling the default processing of the one or moreparticular types of force events is accomplished by executing apredefined method or function call provided by the web browser, which isinvoked by instructions in the web page in response to the will beginevent.

In some embodiments, instructions in the web page that correspond tocertain force events (e.g., a force changed event, a force down event,and/or a force up event) are processed only if default processing ofsuch force events is disabled, because if default processing of suchforce events is not disabled, such force events can be handled by thedefault operations (e.g., based on instructions for default operationsin the web browser).

FIG. 7W illustrates that an intensity threshold (e.g., the low intensitythreshold I_(L)) for generating a mouse down event 784 is distinct froman intensity threshold (e.g., a will begin intensity threshold I_(W))for generating a will begin event 782. This allows the device togenerate, for a touch input with an increasing intensity, a will beginevent 782 before generating a mouse down event 784, thereby providingadditional time to disable (default) operations, for processing one ormore force events, defined by instructions in the web browser.

FIG. 7W also illustrates that, in response to the intensity applied bytouch input 711 on touch-sensitive surface 651 reaching the lowintensity threshold I_(L) (or the intensity applied by touch input 711changing from below the low intensity threshold I_(L) to above the lowintensity threshold I_(L)), the device generates a tactile output of thefirst type (e.g., using tactile output generator(s) 357 in FIG. 3). Atactile output of the first type provides feedback to the userindicating that the intensity of the contact has increased to (or risenabove) the low intensity threshold I_(L). In the example illustrated inFIG. 7T, a mouse down event is generated in temporal proximity to (e.g.,immediately before, during, or immediately after) generation of thetactile output of the first type. As such, the tactile output in FIG. 7Tprovides feedback to the user that a mouse down event associated withthe change in intensity of the contact has been (or will be) generated.

FIGS. 7X-7Y illustrate that touch input 711 on touch-sensitive surface651 moves across touch-sensitive surface 651 and focus selector 706moves across display 650 in accordance with a movement of touch input711 across touch-sensitive surface 651.

FIG. 7X shows user interface 702 before touch input 711 moves acrosstouch-sensitive surface 651. FIG. 7Y shows that touch input 711 hasmoved across touch-sensitive surface 651 and force events thatcorrespond to respective locations on user interface 702 are generated.

Intensity diagram 730 in FIGS. 7X-7Y illustrate that the intensityapplied by touch input 711 on touch-sensitive surface 651 initiallyincreases without moving touch input 711 across touch-sensitive surface651. In response, the device generates force changed event 786 withoutgenerating a mouse moved event.

An overlap of force changed event 788 and mouse moved event 790indicates movement of touch input 711 across touch-sensitive surface 651while changing (e.g., increasing) the intensity applied by touch input711 on touch-sensitive surface 651.

Mouse moved event 792 in FIGS. 7X-7Y (without an associated forcechanged event) indicates movement of touch input 711 acrosstouch-sensitive surface 651 without changing the intensity applied bytouch input 711 on touch-sensitive surface 651.

Force changed event 794 (without an associated mouse moved event) inFIGS. 7X-7Y indicates a change (e.g., decrease) to the intensity appliedby touch input 711 on touch-sensitive surface 651 without movement oftouch input 711 across touch-sensitive surface 651.

Mouse up event 796 in FIGS. 7X-7Y indicates that the intensity appliedby touch input 711 on touch-sensitive surface 651 has reached the lowintensity threshold I_(L) (or the intensity applied by touch input 711on touch-sensitive surface 651 has changed from above the low intensitythreshold I_(L) to below the low intensity threshold I_(L)).

Thus, by using a mouse event and a separate force event, locationschanges of a touch input and intensity changes to the touch input can betracked independently. This simplifies processing changes to touchinputs, thereby improving the efficiency of the device. In addition,this reduces potential errors in processing instructions in certain webpages (e.g., legacy web pages) that are not configured to handle forceevents. For example, if the device generates a mouse moved event inresponse to a change to the intensity applied by a touch input ontouch-sensitive surface 651 and if the web page includes instructions todivide a certain number with a travel distance associated with the touchinput, a change to the intensity applied by a touch input ontouch-sensitive surface 651 without a movement of the touch input acrosstouch-sensitive surface 651 (e.g., zero travel distance) wouldpotentially generate a “division by zero” error. By separating mouseevents and force events, a change to the intensity applied by a touchinput on touch-sensitive surface 651 without a movement of the touchinput across touch-sensitive surface 651 would generate a force event(e.g., a force changed event) without a mouse moved event, and the“division by zero” error can be avoided.

FIG. 7Z illustrates that, in some embodiments, multiple high intensitythresholds are used. In FIG. 7Z, intensity diagram 730 illustrates thatthe intensity applied by touch input 711 on touch-sensitive surface 651reaches a second high intensity threshold I_(H2) (or the intensityapplied by touch input 711 has changed from below the second highintensity threshold I_(H2) to above the second high intensity thresholdI_(H2)). Intensity diagram 730 in FIG. 7Z also illustrates that thedevice generates another force down event 798. Thus, multiple force downevents can be generated for a single touch input at different intensitythresholds (e.g., a first force down event at the (first) high intensitythreshold I_(H) and a second force down event at the second highintensity threshold I_(H2)). Similarly, multiple force up events can begenerated for a single touch input at different intensity thresholds(e.g., a first force up event at the second high intensity thresholdI_(H2) and a second force up event at the (first) high intensitythreshold I_(H)). Although FIG. 7Z illustrates two high intensitythresholds I_(H) and I_(H2), more than two high intensity thresholds areused in some embodiments.

FIG. 7Z also illustrates that, in response to detecting that theintensity applied by touch input 711 on touch-sensitive surface 651 hasreached the second high intensity threshold I_(H2) (or the intensityapplied by touch input 711 changing from below the second high intensitythreshold I_(H2) to above the second high intensity threshold I_(H2)),user interface 702 is updated (e.g., user interface object 714 isdisplayed).

FIGS. 7AA-7FF illustrate generation of certain force events andcorresponding changes to the user interface in accordance with someembodiments.

In FIG. 7AA (which corresponds to FIG. 7B), the user interface includesdisplay of a portion of a web page (e.g., web page 185, FIG. 3) thatincludes image 704, and touch input 707 (e.g., a finger or styluscontact) is detected on touch-sensitive surface 651 at a location thatcorresponds to image 704 of the web page (e.g., focus selector 706, suchas a cursor, is on image 704 of the web page). Intensity diagram 730 inFIG. 7AA indicates that the intensity applied by touch input 707 ontouch-sensitive surface 651 reaches the low intensity threshold I_(L)(or the intensity applied by touch input 707 has changed from below thelow intensity threshold I_(L) to above the low intensity thresholdI_(L)), and the device generates mouse down event 740 and, optionally“will begin” event 742, in response to the intensity applied by touchinput 707 on touch-sensitive surface 651 reaching the low intensitythreshold I_(L) (or the intensity applied by touch input 707 changingfrom below the low intensity threshold I_(L) to above the low intensitythreshold I_(L)).

FIGS. 7BB-7CC illustrate operations when image 704 is not associatedwith a link to additional content (e.g., no hyperlink is associated withimage 704) in accordance with some embodiments.

FIG. 7BB illustrates that the intensity applied by touch input 707 ontouch-sensitive surface 651 continues to increase, and the devicegenerates force changed event 744. The device displays display region708 that includes image 704, and enlarges display region 708 (e.g.,along with image 704 in display region 708) as the intensity applied bytouch input 707 increases. In some embodiments, a smoothing function isapplied (e.g., by the browser application that controls the generationof user interface 702) so that the size of display region 708 and thesize of image 704 smoothly transition with increases and decreases inthe intensity applied by touch input 707.

FIG. 7CC illustrates that the intensity applied by touch input 707 ontouch-sensitive surface 651 reaches the high intensity threshold I_(H)(or the intensity applied by touch input has 707 has changed from belowthe high intensity threshold I_(H) to above the high intensity thresholdI_(H)), and the device displays the enlarged version of image 704 (e.g.,in enlarged display region 708). In FIG. 7CC, the enlarged version ofimage 704 is displayed with at least a portion of the web page.

FIGS. 7DD-7FF illustrate operations when image 704 is associated with alink to additional content (e.g., a hyperlink to another web page isassociated with image 704) in accordance with some embodiments.

FIG. 7DD illustrates that the intensity applied by touch input 707 ontouch-sensitive surface 651 continues to increase, and the devicegenerates force changed event 744. In response, the device displaysdisplay region 716 that includes a preview of the linked content (e.g.,a preview of another web page), and enlarges display region 716 (e.g.,along with the preview in display region 716) as the intensity appliedby touch input 707 increases. In some embodiments, a smoothing functionis applied (e.g., by the browser application that controls thegeneration of user interface 702) so that the size of display region 716(and the preview of the linked content) smoothly transition withincreases and decreases in the intensity applied by touch input 707.

FIG. 7EE illustrates that the intensity applied by touch input 707 ontouch-sensitive surface 651 reaches the high intensity threshold I_(H)(or the intensity applied by touch input has 707 has changed from belowthe high intensity threshold I_(H) to above the high intensity thresholdI_(H)), and the device displays the preview of the linked content (e.g.,in enlarged display region 716). In FIG. 7EE, the preview of the linkedcontent is displayed with at least a portion of the web page.

FIG. 7FF illustrates that the intensity applied by touch input 707 ontouch-sensitive surface 651 has changed from below the low intensitythreshold I_(L) to above the low intensity threshold I_(L) (causing thedevice to generate mouse down event 740), followed by the intensityapplied by touch input 707 on touch-sensitive surfaced 651 falling belowthe low intensity threshold I_(L) (causing the device to generate mouseup event 799). Thus, the intensity applied by touch input 707 ontouch-sensitive surface 651 does not reach the high intensity thresholdI_(H). In response to the sequence of mouse down event 740 and mouse upevent 799, as shown in FIG. 7FF, the device displays the linked content(e.g., another web page) without showing the web page illustrated inFIG. 7AA. In some embodiments, the device (e.g., a browser applicationexecuted by the device) interprets the mouse down event and mouse upevent sequence as a “click” that selects the link associated with image704 (see FIG. 7AA and discussion), thereby causing the device (i.e.,browser application) to display the linked content corresponding to theselected link.

Although FIGS. 7A-7FF illustrate generation of certain force events(e.g., a force down event, a force changed event, a force up event, anda force cancel event), other force events can be used in conjunctionwith at least a subset of the illustrated force events. For example, insome embodiments, the device generates a force cancel event (also calledherein a force cancelled event) in response to determining that,subsequent to generating a will begin event, a touch input ceases to bedetected on the touch-sensitive surface without (or, prior to)generating a force down event (e.g., detecting a release of a touchinput that has satisfied the first intensity threshold but has notsatisfied the second intensity threshold initiates generating a forcecancel event).

FIGS. 8A-8C illustrate a flow diagram of method 800 of processing touchinputs with instructions in a web page in accordance with someembodiments. Method 800 is performed at an electronic device (e.g.,device 300, FIG. 3, or portable multifunction device 100, FIG. 1A) witha display, a touch-sensitive surface, and one or more sensors to detectintensity of contacts with the touch-sensitive surface. In someembodiments, the display is a touch-screen display and thetouch-sensitive surface is on or integrated with the display. In someembodiments, the display is separate from the touch-sensitive surface.Some operations in method 800 are, optionally, combined and/or the orderof some operations is, optionally, changed.

As described below, method 800 provides an enhanced way to process touchinputs with instructions in a web page. Method 800 improves efficiencyin processing touch inputs with instructions in a web page. In addition,method 800 improves compatibility in processing touch inputs withinstructions in legacy web pages.

While displaying a user interface that corresponds to at least a portionof a web page on the display, the device detects (802) a touch input onthe touch-sensitive surface at a first location that corresponds to thedisplayed portion of the web page on the display. For example, as shownin FIG. 7A, touch input 707 is detected on touch-sensitive surface 651.The location of touch input 707 detected on touch-sensitive surface 651corresponds to the location of focus selector 706 in web browser window702 (e.g., a user interface of a web browser application).

In some embodiments, while detecting the touch input on thetouch-sensitive surface, the device receives (804) an input thatcorresponds to a request to generate a mouse down event (e.g., clickingon a mouse button, providing a touch input on the touch-sensitivesurface with sufficient intensity, etc.), and in response to receivingthe input that corresponds to a request to generate a mouse down event,generates the mouse down event. For example, in FIG. 7B, touch input 707is detected on touch-sensitive surface 651, with intensity applied bytouch input 707 reaching the intensity threshold I_(L) (or the intensityapplied by touch input 707 changing from below the intensity thresholdI_(L) to above the intensity threshold I_(L)), and, in response, mousedown event 740 is generated. In some embodiments, the input thatcorresponds to a request to generate a mouse down event is independentof whether the intensity of the touch input on the touch-sensitivesurface has changed from below a first intensity threshold (e.g., aforce down intensity threshold, such as I_(H) in FIG. 7B) to above thefirst intensity threshold. In some embodiments, the input thatcorresponds to a request to generate a mouse down event is based on theintensity of the touch input on the touch-sensitive surface changingfrom below a second intensity threshold, distinct from the firstintensity threshold, to above the second intensity threshold.

In some embodiments, while detecting the touch input on thetouch-sensitive surface (and, in some embodiments, prior to detectingthe intensity of the touch input that has changed from below the firstintensity threshold to above the first intensity threshold), the devicedetects (806) an intensity of the touch input on the touch-sensitivesurface (e.g., with the one or more sensors configured to detectintensity of contacts on the touch-sensitive surface), and determineswhether the intensity of the touch input on the touch-sensitive surfacehas changed from below a second intensity threshold that is distinctfrom the first intensity threshold to above the second intensitythreshold. In response to determining that the intensity of the touchinput on the touch-sensitive surface has changed from below the secondintensity threshold to above the second intensity threshold, the devicegenerates a mouse down event. For example, in FIG. 7B, touch input 707is detected on touch-sensitive surface 651, with intensity applied bytouch input 707 changing from below the intensity threshold I_(L) toabove the intensity threshold I_(L) (or the intensity applied by touchinput 707 reaching the intensity threshold I_(L)), and, in response,mouse down event 740 is generated. In some embodiments, after generatingthe mouse down event, the device provides the mouse down event to theweb page. In some embodiments, after generating the mouse down event,the device processes instructions in the web page that correspond to amouse down event.

In some embodiments, the second intensity threshold is higher than adetection intensity threshold. In some embodiments, the device processesinstructions in the web page (e.g., instructions that correspond to amouse moved event), distinct and separate from instructions in the webpage that correspond to a mouse down event and instructions in the webpage that correspond to a force down event, at least in response todetermining that the intensity of the touch input on the touch-sensitivesurface satisfies the detection intensity threshold (e.g., a mouse movedevent generated in response to a movement of the touch input across thetouch-sensitive surface while the intensity applied by the touch inputsatisfies the detection intensity threshold).

The device detects (808) an intensity of the touch input on thetouch-sensitive surface (e.g., with the one or more sensors). In someembodiments, the intensity of the touch input on the touch-sensitivesurface is detected subsequent to generating a mouse down event (e.g.,operations 804 and/or 808). The device determines (810) whether theintensity of the touch input on the touch-sensitive surface has changedfrom below a first intensity threshold to above the first intensitythreshold. In some embodiments, the first intensity threshold is higherthan the second intensity threshold. In response to determining that theintensity of the touch input on the touch-sensitive surface has changedfrom below the first intensity threshold to above the first intensitythreshold, the device generates (812) a force down event that isdistinct from a mouse down event. For example, FIG. 7D illustrates theintensity of touch input 707 increasing to reach intensity thresholdI_(H) (e.g., the first intensity threshold). FIG. 7D also illustratesgeneration of a force down event (e.g., force down event 746) inresponse to determining that the intensity of touch input 707 ontouch-sensitive surface 651 has reached the intensity threshold I_(H)(or the intensity has changed from below intensity threshold I_(H) toabove intensity threshold I_(H)).

In some embodiments, while detecting the touch input on thetouch-sensitive surface, and in response to determining that theintensity of the touch input on the touch-sensitive surface has changedfrom below the first intensity threshold to above the first intensitythreshold, the device processes (814, FIG. 8B) instructions in the webpage that correspond to the force down event. For example, FIG. 7Rillustrates, in response to determining that the intensity of touchinput 711 on touch-sensitive surface 651 has changed from belowintensity threshold I_(H) (e.g., the first intensity threshold) to aboveintensity threshold I_(H) (e.g., the first intensity threshold),displaying (or locking display of) pop-up view 710 in accordance withinstructions in the web page.

In some embodiments, while detecting the touch input on thetouch-sensitive surface, and subsequent to determining that theintensity of the touch input on the touch-sensitive surface has changedfrom below the first intensity threshold to above the first intensitythreshold, the device determines whether the intensity of the touchinput on the touch-sensitive surface has changed from above a thirdintensity threshold (e.g., a release threshold) to below the thirdintensity threshold. In response to determining that the intensity ofthe touch input on the touch-sensitive surface has changed from abovethe third intensity threshold to below the third intensity threshold,the device generates a force up event that is distinct from the forcedown event. For example, in FIG. 7G, in response to determining that theintensity of touch input 707 has changed from a third intensitythreshold (e.g., I_(H)) to below the third intensity threshold, thedevice generates force up event 750. In some embodiments, the force upevent is distinct from a force down event. In some embodiments, theforce up event is distinct from a mouse down event. In some embodiments,the device processes instructions in the web page that correspond to theforce up event in response to determining that the intensity of thetouch input on the touch-sensitive surface has changed from above thethird intensity threshold to below the third intensity threshold. Insome embodiments, the instructions in the web page that correspond tothe force up event are distinct and separate from the instructions inthe web page that correspond to the force down event (and instructionsin the web page that correspond to a mouse up event and/or instructionsin the web page that correspond to a mouse down event).

In some embodiments, the third intensity threshold is identical to thefirst intensity threshold (e.g., in FIG. 7G, both the first intensitythreshold and the third intensity threshold correspond to I_(H)). Insome embodiments, the third intensity threshold is distinct from thefirst intensity threshold (e.g., the third intensity threshold is lowerthan the first intensity threshold). For example, as shown in FIG. 7L,the third intensity (e.g., I_(HD)) is distinct from the first intensitythreshold (e.g., I_(H)).

In some embodiments, while detecting the touch input on thetouch-sensitive surface, subsequent to determining that the intensity ofthe touch input on the touch-sensitive surface has changed from abovethe third intensity threshold to below the third intensity threshold,the device determines whether the intensity of the touch input on thetouch-sensitive surface has changed from above a fourth intensitythreshold (e.g., a mouse release threshold) to below the fourthintensity threshold, and in response to determining that the intensityof the touch input on the touch-sensitive surface has changed from abovethe fourth intensity threshold to below the fourth intensity threshold,generating a mouse up event that is distinct from the force up event.For example, as shown in FIG. 7M, the intensity of touch input 707changes from above intensity threshold I_(LD) (e.g., a fourth intensitythreshold), to below intensity threshold I_(LD). In some embodiments,the fourth intensity threshold (e.g., I_(LD)) is distinct from thesecond intensity threshold (e.g., I_(L)). In some embodiments, thefourth intensity threshold is identical to the second intensitythreshold (e.g., I_(L)) as shown in FIG. 7I.

In some embodiments, while detecting the touch input on thetouch-sensitive surface, the device determines (818) whether theintensity of the touch input on the touch-sensitive surface has changed,and in response to determining that the intensity of the touch input onthe touch-sensitive surface has changed, generates a force changedevent. For example, in FIG. 7C, force changed event 744 is generated inresponse to determining that the intensity of touch input 707 haschanged (e.g., increased). In some embodiments, in response todetermining that the intensity of the touch input on the touch-sensitivesurface has changed, the device processes instructions in the web pagethat correspond to the force changed event. In some embodiments, theforce changed event is distinct from the force down event and the forceup event. In some embodiments, the instructions that correspond to theforce changed event are distinct and separate from the instructions thatcorrespond to the force down event and/or instructions that correspondto a force up event.

In some embodiments, the device also determines whether the intensity ofthe touch input on the touch-sensitive surface has changed withoutcrossing over the first intensity threshold or the second intensitythreshold, and in response to determining that the intensity of thetouch input on the touch-sensitive surface has changed without crossingover the first intensity threshold or the second intensity threshold,the device generates the force changed event. In some embodiments, thedevice determines that the intensity of the touch input on thetouch-sensitive surface has crossed over the first intensity thresholdor the second intensity threshold, and in response, generates a mousedown event, a force down event, a force up event, or a mouse up eventwithout generating a force changed event.

In some embodiments, the intensity of the touch input on thetouch-sensitive surface must be detected to change by a predeterminedamount before the device generates the force changed event (e.g., thechange in the intensity of the touch input needs to be more than thepredetermined amount to trigger a force changed event). In someembodiments, force changed events are generated in accordance with apredetermined time interval (e.g., force changed events are generated nomore frequent than the predetermined time interval).

In some embodiments, while detecting the touch input on thetouch-sensitive surface, in response to determining that the intensityof the touch input on the touch-sensitive surface has changed anddetermining that the touch input has not moved across thetouch-sensitive surface, the device generates (820) the force changedevent without generating a mouse moved event. For example, in FIG. 7X,because the touch input has not moved across the touch-sensitive surfacewhen generating force changed event 796, a mouse moved event thatcorresponds to a change to a location of the touch input on thetouch-sensitive surface is not generated. Thus, events that correspondto changes to the intensity of the touch input (e.g., force changedevents) and events that correspond to changes to the location of thetouch input (e.g., mouse moved event) are separated. If the device wereconfigured to generate a mouse moved event that corresponds to nochanges to a location of a touch input on the touch-sensitive surface(e.g., no movement of the touch input) in response to a change to theintensity of the touch input on the touch-sensitive surface, certain webpages, designed for mouse moved events that correspond to movements of atouch input across the touch-sensitive surface, may malfunction with amouse moved event that corresponds to no movement of the touch input(e.g., dividing a certain value with a travel distance of the touchinput would generate an error if the travel distance is zero). Thus,preventing generation of the mouse moved event that corresponds to nomovement of the touch input (e.g., by separating force changed eventsand mouse moved events) reduces malfunctions and/or errors in processingsuch web pages.

In some embodiments, the force changed event is generated subsequent todetermining that the intensity of the touch input on the touch-sensitivesurface has changed from below the second intensity threshold to abovethe second intensity threshold and before determining that the intensityof the touch input on the touch-sensitive surface has changed from abovethe fourth intensity threshold to below the fourth intensity threshold.For example, in FIGS. 7A-7J, force changed events are generated onlywhile the intensity of the touch input is above the intensity thresholdI_(L). In some embodiments, generation of the force changed event isforgone prior to determining that the intensity of the touch input onthe touch-sensitive surface has changed from below the second intensitythreshold to above the second intensity threshold (e.g., no forcechanged event is generated in FIG. 7A in response to a change in theintensity of the touch input) and/or after determining that theintensity of the touch input on the touch-sensitive surface has changedfrom above the fourth intensity threshold to below the fourth intensitythreshold (e.g., no force changed event is generated in FIG. 7J inresponse to a change in the intensity of the touch input).Alternatively, the force changed event is generated regardless ofwhether the intensity of the touch input is above the intensitythreshold I_(L). For example, a force changed event is generated inresponse to a change to intensity applied by a touch input even when theintensity of the touch input is below the intensity threshold I_(L), insome embodiments.

In some embodiments, while detecting the touch input on thetouch-sensitive surface, and in response to detecting an input thatincludes movement of the touch input and a change in intensity of thetouch input on the touch-sensitive surface, the device generates (822)one or more mouse moved events that correspond to the touch input andgenerates one or more force changed events that correspond to the touchinput. The one or more force changed events are separate from the one ormore mouse moved events. FIG. 7X illustrates that the device generates,for touch input 711, mouse moved events 790, 792, and 794 and forcechanged events 786, 788, and 796. In some embodiments, at least one ofthe one or more mouse moved events is generated concurrently with arespective force changed event of the one or more force changed events(e.g., mouse moved event 790 is generated concurrently with forcechanged event 788).

In some embodiments, the device provides the one or more force changedevents (and optionally, the one or more mouse moved events) to a website that corresponds to the displayed web page. In some embodiments, inaccordance with a determination that the web site is not configured toaccept force changed events, the one or more mouse moved events areprovided to the website without the one or more force changed events. Inaccordance with a determination that the website is configured to acceptforce changed events, the one or more mouse moved events are provided tothe website along with the one or more force changed events.

In some embodiments, while detecting the touch input on thetouch-sensitive surface, in response to determining that force eventwill begin criteria are satisfied, the device generates (824, FIG. 8C) awill begin event (also called a “force will begin” event) that isdistinct from the mouse down event. In some embodiments, the force eventwill begin criteria are deemed to be satisfied in accordance with adetermination that the intensity of the touch input on thetouch-sensitive surface has changed from a will begin intensitythreshold to above the will begin intensity threshold. In someembodiments, the will begin intensity threshold is the same as thesecond intensity threshold (that corresponds to the mouse down event)(e.g., I_(L) in FIG. 7B). In some embodiments, the will begin intensitythreshold (e.g., I_(W) in FIG. 7W) is distinct from the second intensitythreshold (e.g., lower than the second intensity threshold I_(L)). Insome embodiments, the force event will begin criteria are satisfied inaccordance with a determination that a first application (e.g., asoftware component configured to render web pages, such as Web EngineModule 175 in FIG. 1A, or operating system 126) will initiate a defaultoperation that corresponds to the second intensity threshold (e.g., anoperation that occurs in response to, or is triggered by, the touchinput reaching or exceeding the second intensity threshold). In someembodiments, the default operation is initiated in response to the touchinput exceeding the second intensity threshold by a predeterminedintensity margin (e.g., the default operation does not start immediatelyupon the touch input reaching the second intensity threshold, andrather, waits until the touch input exceeding the second intensitythreshold by the predetermined intensity margin).

In some embodiments, the device is configured to perform defaultoperations in accordance with an intensity of the touch input satisfyingand further exceeding the will begin intensity threshold (e.g., a touchinput that satisfies a force event preview threshold at which a previewof a force-based operation that will be performed when the intensity ofthe touch input reaches the first intensity threshold, where the forceevent preview intensity threshold is greater than the will beginintensity threshold). The will begin event can be used to prevent thedefault operations (e.g., default operations that depend on theintensity of the touch input), and optionally, initiate customoperations defined in the web page (e.g., display of a map as shown inFIG. 7V), instead of the default operations (e.g., display of adictionary lookup as shown in FIG. 7R).

In some embodiments, a combination of the mouse down event and the forcewill begin event is used to determine that the device includes one ormore sensors to detect intensity of contacts with the touch-sensitivesurface (compared to legacy devices that do not include one or moresensors to detect intensity of contacts with the touch-sensitivesurface). For example, a device that does not include one or moresensors to detect intensity of contacts with the touch-sensitive surfacedoes not generate a force will begin event. In some embodiments, inresponse to determining that the device does not include one or moresensors to detect intensity of contacts with the touch-sensitive surface(e.g., based on the absence of the force will begin event), the deviceforgoes processing instructions that correspond to respective forceevents. In some embodiments, a device that includes one or more sensorsto detect intensity of contacts with the touch-sensitive surfacegenerates a force will begin event in temporal proximity to generating amouse down event (e.g., concurrent generation as shown in FIG. 7B orproximate generation as shown in FIG. 7W), and determines that thedevice includes one or more sensors to detect intensity of contacts withthe touch-sensitive surface based on generation of the force will beginevent in temporal proximity to the mouse down event.

In some embodiments, while detecting the touch input on thetouch-sensitive surface, and in response to determining that force eventpreview criteria are satisfied: in accordance with a determination thatthe web page does not include instructions that correspond to the willbegin event, the device processes (826) the touch input in accordancewith (e.g., default) instructions in the first application (e.g., asoftware component configured to rendering web pages, such as Web EngineModule 175 in FIG. 1A) that correspond to the will begin event. Forexample, this includes exemplary default operations such as showing ananimation visually indicating a transition from the mouse down event tothe force down event, showing a dictionary lookup of a correspondingword (if the touch input is detected at a location that corresponds to aword) as shown in FIGS. 7P-7R, and/or showing a preview of a linked webpage (if the touch input is detected at a location that corresponds to ahyperlink or a word or phrase associated with a hyperlink). In someembodiments the force event preview criteria are based on the will beginintensity threshold. In some embodiments, the force event previewcriteria are based on a force event preview intensity threshold that isgreater than the will begin intensity threshold.

In some embodiments, in accordance with a determination that the webpage includes instructions that correspond to the will begin event, thedevice forgoes processing the touch input in accordance with (e.g.,default) instructions in the first application (e.g., a softwarecomponent configured to rendering web pages, such as Web Engine Module175 in FIG. 1A) that correspond to the will begin event (and,optionally, processing the instructions in the web page that correspondto the will begin event). Some examples of customized operations includeshowing a dictionary lookup from a customized dictionary instead of adefault dictionary, preventing display of a preview, and displayingcustomized animations.

In some embodiments, processing the touch input in accordance withinstructions in the web page is conditioned on a setting in the webpage. For example, the web page includes instructions to define aproperty (e.g., “prevent default operations” property) and sets theproperty to either prevent default operations or allow defaultoperations. In accordance with the setting of the property, the deviceconditionally processes the touch input in accordance with instructionsin the web page (e.g., if the property is set to prevent defaultoperations) or in accordance with default instructions (e.g., if theproperty is set to allow default operations). In some embodiments, theproperty is associated with a respective user interface object. Forexample, a first user interface object is associated with a propertythat is set to prevent default operations and a second user interfaceobject is associated with a property that is set to allow defaultoperations. In some embodiments, the property is adjusted while thedevice processes the touch input (or while the device processes theinstructions in the web page). For example, the property is initiallyset to allow default operations, and in accordance with instructions inthe web page, subsequently set to prevent default operations.Alternatively, the property is initially set to prevent defaultoperations, and in accordance with instructions in the web page,subsequently set to allow default operations.

In some embodiments, the instructions in the web page that correspond tothe force down event are processed (828) using a first application(e.g., a software component configured to rendering web pages, such asWeb Engine Module 175 in FIG. 1A), and the device also generates atactile output that corresponds to the force down event using a tactileoutput module (e.g., Haptic Feedback Module 133) that is distinct andseparate from the first application. The tactile output that correspondsto the force down event is generated concurrently with processing theinstructions in the web page that correspond to the force down event.For example, in FIG. 7R, concurrently with (or in temporal proximity to)the touch input reaching the high intensity threshold I_(H), the devicegenerates a tactile output, which serves as a haptic feedback indicatingthat the intensity applied by the touch input has reached the highintensity threshold I_(H). In the example shown in FIG. 7R, the devicealso generates force down event 770 in response to the touch input 711reaching the high intensity threshold I_(H).

In some embodiments, the tactile output that corresponds to the forcedown event (e.g., force down event 770, FIG. 7R) is generated using thetactile output module without sending instructions from the firstapplication to the tactile output module. For example, in FIG. 1A,contact/motion module 130 determines that the intensity of the touchinput on the touch-sensitive surface has changed from below the firstintensity threshold to above the first intensity threshold, and sendsinstructions or signals to both haptic feedback module 133 and webengine module 175. Haptic feedback module 133 initiates providing atactile output (e.g., using haptic feedback controller 161 and tactileoutput generator(s) 163) while web engine module 175 independentlyprocesses instructions in web page 185 to update the display. Thus,although operations of haptic feedback module 133 and web engine module175 are coordinated (by the contact/motion module 130), there is no needfor web engine module 175 to send instructions to haptic feedback module133 or for haptic feedback module 133 to send instructions to web enginemodule 175. This reduces the operational burden on Web Engine Module175, and thus, improves the efficiency in processing touch inputs inaccordance with instructions in the web page (and providing tactileoutputs).

In some embodiments, the device generates a tactile output thatcorresponds to the force up event using the tactile output module (e.g.,Haptic Feedback Module 133) that is distinct and separate from the firstapplication (e.g., Web Engine Module 175). In some embodiments, thetactile output that corresponds to the force up event is generated usingthe tactile output module without sending instructions from the firstapplication to the tactile output module. In some embodiments, thetactile output module generates the tactile output based on theintensity determined by the one or more sensors.

In some embodiments, the force down and force up events are generated bya software component other than the first application (e.g.,contact/motion module 130) and provided to the first application (e.g.,Web Engine Module 175) so that the first application updates the userinterface in coordination with the tactile output to be generated by thetactile output module when the touch input reaches the triggeringintensity threshold. In this example, the tactile output is notgenerated in response the force down event (because the force down eventis not sent to the tactile output module), rather, the force down eventis provided to the first application to generate a visual or audibleoutput in conjunction with the tactile output (if it is configured to doso). The tactile outputs are generated in response to signals orinstructions, other than force down events or force up events.

In some embodiments, the first location on the touch-sensitive surfacecorresponds (830) to a first user interface object. The instructions inthe web page that correspond to the mouse down event correspond to thefirst user interface object, and the instructions in the web page thatcorrespond to the force down event correspond to the first userinterface object. For example, instructions in the web page areconfigured to operate with respect to respective user interface objects(e.g., a first set of instructions for a force down event is configuredfor processing a force down event that corresponds to a first userinterface object and a second set of instructions for a force down eventis configured for processing a force down event that corresponds to asecond user interface object). FIG. 7T illustrates generation of a mousedown event (e.g., highlighting the text “Gettysburg”) that correspondsto the text “Gettysburg” (e.g., a first user interface object) underfocus selector 706, and FIG. 7V illustrates generation of a force downevent (e.g., displaying and/or locking pop-up view 712) that correspondsto the text “Gettysburg” (e.g., the first user interface object).

In some embodiments, the web page defines a plurality of user interfaceobjects and includes a plurality of sets of instructions that correspondto a force down event. Respective sets of instructions correspond to aforce down event for respective user interface objects. For example, theweb page includes (i) information defining the first user interfaceobject and a second user interface object and (ii) instructions thatcorrespond to a force down event for the first user interface object andinstructions that correspond to a force down event for the second userinterface object. Similarly, the web page may include location-specificor user-interface-object-specific instructions that correspond to eventsof different types (e.g., force up event, force changed event, and willbegin event). In some embodiments, the web page includes (i) informationdefining the first user interface object and the second user interfaceobject and (ii) instructions that correspond to a will begin event forthe first user interface object and instructions that correspond to awill begin event for the second user interface object.

It should be understood that the particular order in which theoperations in FIGS. 8A-8C have been described is merely exemplary and isnot intended to indicate that the described order is the only order inwhich the operations could be performed. One of ordinary skill in theart would recognize various ways to reorder the operations describedherein. For example, in some embodiments, a method performed at anelectronic device with a touch-sensitive surface, a display, and one ormore sensors to detect intensity of contacts with the touch-sensitivesurface includes, while displaying a user interface that corresponds toat least a portion of a web page on the display, detecting a touch inputon the touch-sensitive surface at a first location that corresponds tothe displayed portion of the web page on the display. The method alsoincludes, while detecting the touch input on the touch-sensitivesurface, detecting an intensity of the touch input on thetouch-sensitive surface (e.g., with the one or more sensors);determining whether the intensity of the touch input on thetouch-sensitive surface has changed from below a first intensitythreshold (e.g., a low intensity threshold, such as a mouse downintensity threshold) to above the first intensity threshold; and, inresponse to determining that the intensity of the touch input on thetouch-sensitive surface has changed from below the first intensitythreshold to above the first intensity threshold, generating a mousedown event (and optionally, processing instructions in the web page thatcorrespond to a mouse down event). The method further includes,subsequent to determining that the intensity of the touch input on thetouch-sensitive surface has changed from below the first intensitythreshold to above the first intensity threshold, detecting theintensity of the touch input on the touch-sensitive surface; determiningwhether the intensity of the touch input on the touch-sensitive surfacehas changed from below a second intensity threshold (e.g., a highintensity threshold, such as a force down intensity threshold) that isdistinct from the first intensity threshold to above the secondintensity threshold; and, in response to determining that the intensityof the touch input on the touch-sensitive surface has changed from belowthe second intensity threshold to above the second intensity threshold,generating a force down event that is distinct from the mouse downevent. For brevity, these details are not repeated herein.

Additionally, it should be noted that details of other processesdescribed herein with respect to other methods described herein (e.g.,method 900) are also applicable in an analogous manner to method 800described above with respect to FIGS. 8A-8C. For example, the web pages,touch inputs, user interface objects, intensity thresholds, andanimations described above with reference to method 800 optionally haveone or more of the characteristics of the web pages, touch inputs, userinterface objects, intensity thresholds, and animations described hereinwith reference to other methods described herein (e.g., method 900). Forbrevity, these details are not repeated here.

FIG. 9 is a flow diagram illustrating method 900 of processing touchinputs based on an association of displayed content in accordance withsome embodiments. Method 900 is performed at an electronic device (e.g.,device 300, FIG. 3, or portable multifunction device 100, FIG. 1A) witha display, a touch-sensitive surface, and one or more sensors to detectintensity of contacts with the touch-sensitive surface. In someembodiments, the display is a touch-screen display and thetouch-sensitive surface is on or integrated with the display. In someembodiments, the display is separate from the touch-sensitive surface.Some operations in method 900 are, optionally, combined and/or the orderof some operations is, optionally, changed.

As described below, method 900 provides an enhanced way to process touchinputs based on displayed content. Method 900 improves efficiency inaccessing information associated with web pages. For example, byproviding an enlarged image in response to a touch input on an imagewhen the image is not associated with a linked content (e.g., notassociated with a hyperlink) and providing a preview of the linkedcontent in response to a touch input on an image when the image isassociated with the linked content (e.g., associated with a hyperlink),method 900 provides additional information (be it an enlarged image or apreview of a linked content) associated with the image, therebyfacilitating use of the information on the web page. In somecircumstances, efficiency is increased because the additionalinformation (e.g., preview of the linked content) enables the user toavoid selecting content (and thus switching to a new contextcorresponding to that content) not of current interest to the user, andto concentrate the user's efforts on other content more directly ofcurrent interest to the user.

The device displays (902), on the display, a content region includingfirst content that contains an image (e.g., the web page with image 704,as shown in FIG. 7AA).

In some embodiments, the content region is (904) a content region of aweb browser. The first content is a first web page. The image is animage in the first web page. For example, the user interface shown inFIG. 7AA is a user interface of a web browser that includes display of aweb page with image 704 in the web page.

While displaying the first content in the content region on the display,the device detects (906) an input at a location that corresponds to thelocation of the image on the display (e.g., touch input 707 ontouch-sensitive surface 651 while focus selector 706 is positioned overimage 704, or a touch input on display 650 over image 704 when display650 is a touch-sensitive display).

In response to detecting the input, the device, in accordance with adetermination that the input includes an intensity above a respectivethreshold and that the image is associated with a link to second contentthat is different from the first content, displays (908) a preview ofthe second content while maintaining display of at least a portion ofthe first content in the content region. For example, in FIG. 7EE, theintensity applied by touch input 707 reaches (or exceeds) the highintensity threshold I_(H) (and image 704 is associated with a link to adifferent web page). In response, the device displays a preview of thelinked content in display region 716 while a portion of the web pageremains on display 650.

In some embodiments, the second content is (910) a second web page. Thelink to the second content is a hyperlink to the second web page that isassociated with the image. For example, in FIGS. 7DD-7EE, image 704 isassociated with a hyperlink to the second web page (e.g., the web pageincludes HTML tags, such as <a href=“URL of the second page”><imgsrc=“filename of image 704” width=“100” height=“100” border=“0” ></a>).

In accordance with a determination that the input includes an intensityabove the respective threshold and that the image is not associated witha link to additional content, the device displays (912) an enlargedversion of the image while maintaining display of at least a portion ofthe first content in the content region. For example, in FIG. 7CC, theintensity applied by touch input 707 reaches (or exceeds) the highintensity threshold I_(H) (and image 704 is not associated with a linkto a different web page). In response, the device displays an enlargedversion of image 704 in display region 708 while a portion of the webpage remains on display 650.

In some embodiments, displaying the preview of the second contentincludes (914) enlarging the image as the intensity of the inputincreases (e.g., display region 708 and the image in display region 708enlarge as the intensity of touch input 707 increases, as shown in FIGS.7BB-7CC). Displaying the enlarged version of the image includesenlarging the preview as the intensity of the input increases (e.g.,display region 716 and the preview in display region 716 enlarge as theintensity of touch input 707 increases, as shown in FIGS. 7DD-7EE). Insome embodiments, the touch-sensitive surface and the display areintegrated (e.g., a touch-sensitive display) and the input is detectedon the touch-sensitive display. In some embodiments, the image enlargesas the intensity of the input on the touch-sensitive display increases.In some embodiments, the preview enlarges as the intensity of the inputon the touch-sensitive display increases.

In some embodiments, the device, in response to detecting the input andin accordance with a determination that the input does not include anintensity above the respective threshold and that the image isassociated with a link to the second content, replaces (916) display ofthe first content in the content region with the second content. Forexample, as shown in FIG. 7FF, in response to detecting touch input 707and in accordance with a determination that the intensity of touch input707 does not reach (or exceed) the high intensity threshold I_(H) (andimage 704 is associated with a link to a different web page), display ofthe web page (shown in FIG. 7AA) is replaced with display of the linkedweb page (e.g., as in response to a conventional mouse click on ahyperlinked object on a web page). Alternatively, in some embodiments,the determination that causes the device to replace the display of thefirst content in the content region with second content is adetermination that the intensity of the input increases above firstthreshold (e.g., low threshold, I_(L), FIG. 7EE) and then decreasesbelow the first threshold without increasing above the respectivethreshold (e.g., high threshold, I_(H), FIG. 7EE).

In some embodiments, the device, in response to detecting the input andin accordance with a determination that the input does not include anintensity above the respective threshold and that the image is notassociated with a link to additional content, maintains (918) display ofthe first content in the content region. For example, display of the webpage remains on the display, as shown in FIG. 7C (e.g., as in responseto a conventional mouse click on a web page object that is notassociated with a hyperlink).

It should be understood that the particular order in which theoperations in FIG. 9 have been described is merely exemplary and is notintended to indicate that the described order is the only order in whichthe operations could be performed. One of ordinary skill in the artwould recognize various ways to reorder the operations described herein.Additionally, it should be noted that details of other processesdescribed herein with respect to other methods described herein (e.g.,method 800) are also applicable in an analogous manner to method 900described above with respect to FIG. 9. For example, the web pages,touch inputs, user interface objects, intensity thresholds, andanimations described above with reference to method 900 optionally haveone or more of the characteristics of the web pages, touch inputs, userinterface objects, intensity thresholds, and animations described hereinwith reference to other methods described herein (e.g., method 800). Forbrevity, these details are not repeated here.

The operations in the information processing methods described aboveare, optionally implemented by running one or more functional modules ininformation processing apparatus such as general purpose processors(e.g., as described above with respect to FIGS. 1A and 3) or applicationspecific chips.

The operations described above with reference to FIGS. 8A-8C and FIG. 9are, optionally, implemented by components depicted in FIGS. 1A-1B. Forexample, intensity detection operation 808, event generation operation812, and instruction processing operation 814 are, optionally,implemented by event sorter 170, event recognizer 180, and event handler190. Event monitor 171 in event sorter 170 detects a contact ontouch-sensitive display 112, and event dispatcher module 174 deliversthe event information to application 136-1. A respective eventrecognizer 180 of application 136-1 compares the event information torespective event definitions 186, and determines whether a first contactat a first location on the touch-sensitive surface (or whether rotationof the device) corresponds to a predefined event or sub-event, such asselection of an object on a user interface, or rotation of the devicefrom one orientation to another. When a respective predefined event orsub-event is detected, event recognizer 180 activates an event handler190 associated with the detection of the event or sub-event. Eventhandler 190 optionally uses or calls data updater 176 or object updater177 to update the application internal state 192. In some embodiments,event handler 190 accesses a respective GUI updater 178 to update whatis displayed by the application. Similarly, it would be clear to aperson having ordinary skill in the art how other processes can beimplemented based on the components depicted in FIGS. 1A-1B.

The foregoing description, for purpose of explanation, has beendescribed with reference to specific embodiments. However, theillustrative discussions above are not intended to be exhaustive or tolimit the invention to the precise forms disclosed. Many modificationsand variations are possible in view of the above teachings. Theembodiments were chosen and described in order to best explain theprinciples of the invention and its practical applications, to therebyenable others skilled in the art to best use the invention and variousdescribed embodiments with various modifications as are suited to theparticular use contemplated.

What is claimed is:
 1. A method, comprising: at an electronic devicewith a display, a touch sensitive surface and one or more sensors thatare configured to detect the intensity of inputs on the touch-sensitivesurface: displaying, on the display, a content region including firstcontent that contains an image; while displaying the first content inthe content region on the display, detecting an input at a location thatcorresponds to the location of the image on the display; and, inresponse to detecting the input: in accordance with a determination thatthe input includes an intensity above a respective threshold and thatthe image is associated with a link to second content that is differentfrom the first content, displaying a preview of the second content whilemaintaining display of at least a portion of the first content in thecontent region; and, in accordance with a determination that the inputincludes an intensity above a respective threshold and that the image isnot associated with a link to additional content, displaying an enlargedversion of the image while maintaining display of at least a portion ofthe first content in the content region.
 2. The method of claim 1,including, in response to detecting the input, in accordance with adetermination that the input does not include an intensity above therespective threshold and that the image is associated with a link to thesecond content, replacing display of the first content in the contentregion with the second content.
 3. The method of claim 1, including, inresponse to detecting the input, in accordance with a determination thatthe input does not include an intensity above the respective thresholdand that the image is not associated with a link to additional content,maintaining display of the first content in the content region.
 4. Themethod of claim 1, wherein the content region is a content region of aweb browser, the first content is a first web page, and the image is animage in the first web page.
 5. The method of claim 1, wherein thesecond content is a second web page and the link to the second contentis a hyperlink to the second web page that is associated with the image.6. The method of claim 1, wherein: displaying the preview of the secondcontent includes enlarging the preview as the intensity of the inputincreases; and displaying the enlarged version of the image includesenlarging the image as the intensity of the input increases.
 7. Anelectronic device, comprising: a display; a touch-sensitive surface; oneor more sensors to detect intensity of contacts with the touch-sensitivesurface; one or more processors; memory; and one or more programs,wherein the one or more programs are stored in the memory and configuredto be executed by the one or more processors, the one or more programsincluding instructions for: displaying, on the display, a content regionincluding first content that contains an image; while displaying thefirst content in the content region on the display, detecting an inputat a location that corresponds to the location of the image on thedisplay; and, in response to detecting the input: in accordance with adetermination that the input includes an intensity above a respectivethreshold and that the image is associated with a link to second contentthat is different from the first content, displaying a preview of thesecond content while maintaining display of at least a portion of thefirst content in the content region; and, in accordance with adetermination that the input includes an intensity above a respectivethreshold and that the image is not associated with a link to additionalcontent, displaying an enlarged version of the image while maintainingdisplay of at least a portion of the first content in the contentregion.
 8. The electronic device of claim 7, wherein the one or moreprograms include instructions for: in response to detecting the input,in accordance with a determination that the input does not include anintensity above the respective threshold and that the image isassociated with a link to the second content, replacing display of thefirst content in the content region with the second content.
 9. Theelectronic device of claim 7, wherein the one or more programs includeinstructions for: in response to detecting the input, in accordance witha determination that the input does not include an intensity above therespective threshold and that the image is not associated with a link toadditional content, maintaining display of the first content in thecontent region.
 10. The electronic device of claim 7, wherein thecontent region is a content region of a web browser, the first contentis a first web page, and the image is an image in the first web page.11. The electronic device of claim 7, wherein the second content is asecond web page and the link to the second content is a hyperlink to thesecond web page that is associated with the image.
 12. The electronicdevice of claim 7, wherein: displaying the preview of the second contentincludes enlarging the preview as the intensity of the input increases;and displaying the enlarged version of the image includes enlarging theimage as the intensity of the input increases.
 13. A non-transitorycomputer readable storage medium storing one or more programs, the oneor more programs comprising instructions, which, when executed by anelectronic device with a display, a touch-sensitive surface, and one ormore sensors to detect intensity of contacts with the touch-sensitivesurface, cause the device to: display, on the display, a content regionincluding first content that contains an image; while displaying thefirst content in the content region on the display, detect an input at alocation that corresponds to the location of the image on the display;and, in response to detecting the input: in accordance with adetermination that the input includes an intensity above a respectivethreshold and that the image is associated with a link to second contentthat is different from the first content, display a preview of thesecond content while maintaining display of at least a portion of thefirst content in the content region; and, in accordance with adetermination that the input includes an intensity above a respectivethreshold and that the image is not associated with a link to additionalcontent, display an enlarged version of the image while maintainingdisplay of at least a portion of the first content in the contentregion.
 14. The non-transitory computer readable storage medium of claim13, wherein the one or more programs include instructions, which, whenexecuted by an electronic device, cause the electronic device, inresponse to detecting the input, and in accordance with a determinationthat the input does not include an intensity above the respectivethreshold and that the image is associated with a link to the secondcontent, to replace display of the first content in the content regionwith the second content.
 15. The non-transitory computer readablestorage medium of claim 13, wherein the one or more programs includeinstructions, which, when executed by an electronic device, cause theelectronic device, in response to detecting the input, and in accordancewith a determination that the input does not include an intensity abovethe respective threshold and that the image is not associated with alink to additional content, to maintain display of the first content inthe content region.
 16. The non-transitory computer readable storagemedium of claim 13, wherein the content region is a content region of aweb browser, the first content is a first web page, and the image is animage in the first web page.
 17. The non-transitory computer readablestorage medium of claim 13, wherein the second content is a second webpage and the link to the second content is a hyperlink to the second webpage that is associated with the image.
 18. The non-transitory computerreadable storage medium of claim 13, wherein: displaying the preview ofthe second content includes enlarging the preview as the intensity ofthe input increases; and displaying the enlarged version of the imageincludes enlarging the image as the intensity of the input increases.